Skip to content

Rebuild the Lazurio overlay on upstream T3 Code v0.1.8 - #187

Closed
immakermatty wants to merge 542 commits into
mainfrom
lazurio/rebuild-v0.1.8
Closed

immakermatty wants to merge 542 commits into
mainfrom
lazurio/rebuild-v0.1.8

Conversation

@immakermatty

@immakermatty immakermatty commented Nov 10, 2026 •

Copy link
Copy Markdown

Status: ready for review on the exact head 9a4a521cdd. Lazurio Fork CI is green on it (https://github.com/Lazurio/t3code/actions/runs/42783501819, all four required checks). This is the rebuild of the Lazurio overlay on upstream T3 Code v0.1.8 (stages 2–8 of docs/operations/lazurio-fork-release.md). It is never merged by its button: its head becomes main through the swap in stage 6, after an approval on this exact head.

Rebuild issue: #185 (inventory, every row's decision A1–A14, the compatibility gates). Stage 3's checks and their evidence: #185 (comment)

Inputs

Old base v0.1.7 = 322f6544dfad0a3c8a0c8cbecf2c7f7874b14268 (main's base)
New base v0.1.8 = bf469bb19669671d0df2efda74ed73867a7137c0
Source stack main's rows, taken from git log --reverse v0.1.7..origin/main by subject
expected_old_main cab18ad99be7d16dfd32a1cb1552f8ab0e9e3dc5 (v0.1.7-lazurio.1)
candidate_head 9a4a521cdd2969f2382838f7803de92a6326cb42

What the rebuild does

main's rows are replayed onto v0.1.8 as one commit per row, in the target stack's order, with row 5 (distribution) last: 32 commits. Every row v0.1.8 changed has an "On v0.1.8" paragraph in its commit message. overlay-delta.sh v0.1.7 origin/main v0.1.8 HEAD reports 32 of 297 files whose overlay changes differ; each one is explained below and, with file:line on v0.1.8, in #185.

Rows that changed behaviour or shape:

The other rows keep their seams; their changes were imports and neighbouring blocks.

Distribution (row 5)

What stays the same (stage 5, details in #185)

  • Protocols: launcher protocol 3 (apps/server/src/cloud/serviceProtocol.ts:4) and orchestration protocol 2 (packages/contracts/src/environment.ts:13).
  • Database: v0.1.8 adds migration 080_ScheduledTaskThreadMode; the overlay adds none. The upgrade is one-way, so a database backup comes before every update to 0.1.8 (A11).
  • Dictation (transcribe-cpp) is best-effort on Environments (A12): the image and archives must start, and missing dictation must not stop the server.

Verified locally on 9a4a521cdd

  • vp fmt --check over the repository (7100 files): clean. vp lint: exit 0, upstream warnings only. Typecheck of the affected packages: exit 0. knip: no findings in overlay files.
  • Contract test 51/51. Allowlist guard in both directions: 131/131.
  • Tests beside the overlay's changes (Fork CI's selection):
    • server: 83 files pass and 1 is skipped (1580 tests);
    • client-runtime 16, contracts 20, effect-acp 33, shared 5, scripts 14.
  • Web: 66 files, run one at a time on Playwright's Chromium: all pass, 2363 tests, no unhandled errors. Running all 66 in one process aborted twice on route.fulfill: The object has been collected to prevent unbounded heap growth in @vitest/browser-playwright; each file passes alone.
  • Mutations, each failing a test:
    • the A7 and A8 contract pins;
    • row 10 without fullScreenshot;
    • row 20 with the code API behind a read scope, and with the ceiling check disabled;
    • row 28's guard on the wrong value;
    • row 22 without the request_secret sentence;
    • row 30 setting steersRunId for a fresh session.
  • No overlay test was dropped. The two test cases that left the files since main were upstream's, removed upstream in fix(server): background command results reach a running Codex goal pingdotgg/t3code#33268 and feat(settings): clean up Labs: promote tool calls, remove plan mode and old toggles pingdotgg/t3code#33131.
  • 15a, release version check from a clean git archive HEAD against the live release list: 0.1.8-preview.20261110.1 and 0.1.8-lazurio.1 pass.
  • Public-repo scan over git diff v0.1.8 HEAD, the commit messages and this description: every match is an existing overlay term.
  • Independent check: three read-only reviews (rows 1–13; 15–24; 25–34 and 5). Every finding was fixed or recorded; the table is in Přestavba na upstream T3 Code v0.1.9 #185. Out of scope and filed: Agent commands' request namespace keys on a label any OAuth MCP client can register #186.

Not verified yet:

  • the split of the agent context budget between overlay and upstream (A14);
  • the Buddy surface items N1 and N2 and the /welcome and install.sh texts (U2, U3) in a browser;
  • anything on canary, which stage 7 covers on Ring 0.

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · bot c59bfd74-62a6-4eaa-88dd-5e19f1b3032e

🤖 Generated with Claude Code

Note

Rebuild the Lazurio overlay on upstream T3 Code v0.1.8

  • Re-lands the Lazurio overlay on the new upstream base. The server gains a managed-folder mode driven by T3CODE_LAZURIO_FOLDER (managedFolderConfig.ts), guarded project/turn/auth services (runtimeLayer.ts), and new Buddy-surface and acting-sender routes and behaviors.
  • Adds a full voice/speech stack: server speech model registry and filler-word removal, native live voice transcription on Android (API 31+) and iOS, environment/cloud transcription routes, a new web voice settings page, and dictation shortcuts in the web and preview composers.
  • Reworks mobile native UI around T3NativeControls: native SheetHeader/AppBar, SegmentedControl, SecretTextInput, FrostedCutout, and an Android split-view workspace layout with native headers and inspector panes.
  • Splits executable builds into a bootstrap plus separate embedded CLI asset, rejecting bootstraps over 1 MiB (cli.ts); switches typechecking repo-wide from tsc to effect-tsgo tsrs.
  • Many fixes ride along: snooze no longer wakes on pending user input, Claude model manifest refresh, PR action mutations now return full pull-request summaries, unresolved settings secrets surface as SettingsSecretUnresolvedError instead of empty values, and SQLite WAL limit rises to 128 MiB.
  • Risk: overlay rebuild touches nearly every subsystem; key things to verify are the runtime layer guards in runtimeLayer.ts, the snooze logic change in threadSettled.ts, and the secret-resolution behavior change in settingsSecretValue.ts where unreadable secrets now stay unresolved rather than resolving as empty.

Macroscope summarized 9a4a521.

juliusmarminge and others added 30 commits November 6, 2026 12:11
…er a restart (pingdotgg#32162)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…ing in from the corner (pingdotgg#32141)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
… the full width (pingdotgg#32142)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…25988)

Co-authored-by: maria-rcks <maria@kuuro.net>
Co-authored-by: Julius Marminge <julius0216@outlook.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Julius Marminge <51714798+juliusmarminge@users.noreply.github.com>
…ild (pingdotgg#31945)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…ace (pingdotgg#31936)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…ping or garbling (pingdotgg#31168)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: maria-rcks <maria@kuuro.net>
…29355)

Co-authored-by: PR Batch Tester <agent@local.test>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: GPT-6.1 Sol <noreply@openai.com>
Co-authored-by: maria-rcks <maria@kuuro.net>
…gdotgg#28530)

Co-authored-by: PR Batch Tester <agent@local.test>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…onto an empty ~/.t3 (pingdotgg#23878)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
pingdotgg#31769)

Co-authored-by: Aditya Vardhan Sharma <adityaradhika13@gmail.com>
Co-authored-by: Lakshmi Tanmay <lakshmi@voltcrash.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
pingdotgg#32035)

Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
…#32325)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…2269)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…32263)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
@agentrozjedemeai

Copy link
Copy Markdown
Collaborator

Blocking

Bez blokujícího nálezu.

Non-blocking

Bez dalších nálezů. Prošel jsem diff overlaye proti bf469bb196 pro níže uvedených 76 různých souborů (83 dotyků souborů v pěti řádcích) a range-diff řádků 15–19: fe6770a606, 3ecdc2f050, 3486ee3ddf, b49c0e9044, f77105df22. Ověřil jsem popsané změny /welcome, zachování ProjectOperationError podle A3, úpravu odesílání a testovacího dvojníka přihlášení proti rozhodnutím v #185. Tag upstreamu v0.1.8 odpovídá bf469bb19669671d0df2efda74ed73867a7137c0. Testy jsem dle zadání znovu nespouštěl.

Prošlé soubory:

  • apps/server/src/binCli.ts
  • apps/server/src/cli/config.ts
  • apps/server/src/config.ts
  • apps/server/src/environment/ServerEnvironment.ts
  • apps/server/src/lazurio/cli.test.ts
  • apps/server/src/lazurio/cli.ts
  • apps/server/src/lazurio/managedFolder.test.ts
  • apps/server/src/lazurio/managedFolder.testkit.ts
  • apps/server/src/lazurio/managedFolder.ts
  • apps/server/src/lazurio/managedFolderConfig.test.ts
  • apps/server/src/lazurio/managedFolderConfig.ts
  • apps/server/src/lazurio/managedFolderGuards.test.ts
  • apps/server/src/lazurio/managedFolderGuards.ts
  • apps/server/src/lazurio/managedFolderStartup.test.ts
  • apps/server/src/lazurio/managedFolderStartup.ts
  • apps/server/src/lazurio/managedFolderVcs.test.ts
  • apps/server/src/lazurio/modelRecommendation.test.ts
  • apps/server/src/lazurio/modelRecommendation.ts
  • apps/server/src/lazurio/modelRecommendationRoute.test.ts
  • apps/server/src/lazurio/modelRecommendationRoute.ts
  • apps/server/src/lazurio/overlay.ts
  • apps/server/src/lazurio/providerRefresh.test.ts
  • apps/server/src/lazurio/providerRefresh.ts
  • apps/server/src/lazurio/providerRefreshRoute.test.ts
  • apps/server/src/lazurio/providerRefreshRoute.ts
  • apps/server/src/lazurio/providerSignIn.test.ts
  • apps/server/src/lazurio/providerSignIn.ts
  • apps/server/src/lazurio/serverBrowser.test.ts
  • apps/server/src/orchestration-v2/runtimeLayer.ts
  • apps/server/src/server.ts
  • apps/server/src/serverRuntimeStartup.ts
  • apps/server/src/serverSettings.ts
  • apps/server/src/vcs/VcsProvisioningService.ts
  • apps/server/src/ws.ts
  • apps/web/index.html
  • apps/web/public/manifest.webmanifest
  • apps/web/src/branding.logic.ts
  • apps/web/src/branding.ts
  • apps/web/src/bundledDev.test.ts
  • apps/web/src/components/CommandPalette.tsx
  • apps/web/src/components/GitActionsControl.tsx
  • apps/web/src/components/Sidebar.tsx
  • apps/web/src/components/chat/DraftHeroHeadline.tsx
  • apps/web/src/components/chat/TimelineUserMessageRow.tsx
  • apps/web/src/components/chat/useComposerSend.ts
  • apps/web/src/components/onboarding/FirstRunGate.tsx
  • apps/web/src/components/settings/AddProviderInstanceDialog.tsx
  • apps/web/src/components/settings/CodexSetupSection.tsx
  • apps/web/src/components/sidebar/SidebarChrome.tsx
  • apps/web/src/components/sidebar/SidebarThreadHeader.tsx
  • apps/web/src/environments/primary/auth.ts
  • apps/web/src/hooks/useHandleNewThread.test.ts
  • apps/web/src/hooks/useHandleNewThread.ts
  • apps/web/src/lazurio/LazurioBadge.tsx
  • apps/web/src/lazurio/LazurioSignIn.browser.test.tsx
  • apps/web/src/lazurio/LazurioSignIn.managedPolicy.browser.test.tsx
  • apps/web/src/lazurio/LazurioSignIn.tsx
  • apps/web/src/lazurio/brand/README.md
  • apps/web/src/lazurio/brand/symbol-color-dark.svg
  • apps/web/src/lazurio/brand/symbol-color.svg
  • apps/web/src/lazurio/branding.test.ts
  • apps/web/src/lazurio/environmentPairing.test.ts
  • apps/web/src/lazurio/environmentPairing.ts
  • apps/web/src/lazurio/managedFirstRun.ts
  • apps/web/src/lazurio/managedFolder.test.ts
  • apps/web/src/lazurio/managedFolder.ts
  • apps/web/src/lazurio/managedPromptLinks.ts
  • apps/web/src/lazurio/providerSignIn.test.ts
  • apps/web/src/lazurio/providerSignIn.ts
  • apps/web/src/lazurio/starPrompt.test.ts
  • apps/web/src/lazurio/starPrompt.ts
  • apps/web/src/lazurio/theme.css
  • apps/web/src/lib/bootError.ts
  • apps/web/src/main.tsx
  • apps/web/src/routes/welcome.tsx
  • packages/contracts/src/server.ts

Agent: environment unknown · bot 7f4c95eb-ae6f-46bc-a357-a989033d2686

— Pablo

@agentrozjedemeai

Copy link
Copy Markdown
Collaborator

Blocking

  • Není doloženo splnění A12 — .github/workflows/lazurio-fork-ci.yml:539 a Dockerfile.lazurio:68. Rozhodnutí A12 v issue #185 výslovně podmiňuje převzetí diktování jako best-effort tím, že image a archivy spustí server a jeho proces přežije chybějící transcribe-cpp. Zápis brány Machines a Platformy zatím říká jen „ověřit v image“; doklad etapy 3 tento scénář neuvádí. Zelené CI image sestaví, ale spouští ho pouze s --version a kontroluje soubory, nikoli běh serveru bez diktování. Doplňte ověření obou distribučních forem a chybějící komponenty a jeho výsledek na přesném kandidátovi zapište do issue. Jinak nelze posoudit, zda nová báze nespadne při startu či při nedostupném diktování.

Non-blocking

  • Piny SidebarControl, ComposerControlsBar, pořadí návrhu promptu, A7 a A8 odpovídají příslušným švům; obě verze protokolu zůstávají 3 a 2. Migrace 080 je uvedena spolu s požadavkem zálohy.
  • Canarová kontrola tlačítka Update, párování a uživatelského rozhraní podle issue zůstává budoucím krokem. Testy jsem znovu nespouštěl podle zadání; CI 42783501819 je zelené na tomto headu.

Prošlé soubory

Řádky 1, 2, 3, 4, 34 a 5: commity 0595470689, 8015afd811, a6d954560a, f36373c7f1, fd4915f89e, 9a4a521cdd; 64 různých souborů (68 započtení po jednotlivých commitech):

  • .agents/skills/lazurio-upstream-rebuild/SKILL.md
  • .agents/skills/lazurio-upstream-rebuild/agents/openai.yaml
  • .dockerignore
  • .github/ISSUE_TEMPLATE/1-lazurio-t3-code.yml
  • .github/README.md
  • .github/SECURITY.md
  • .github/workflows/lazurio-cli-archives.yml
  • .github/workflows/lazurio-fork-ci.yml
  • .github/workflows/lazurio-release.yml
  • .github/workflows/lazurio-upstream-watch.yml
  • Dockerfile.lazurio
  • apps/server/src/auth/EnvironmentAuthPolicy.test.ts
  • apps/server/src/auth/EnvironmentAuthPolicy.ts
  • apps/server/src/auth/McpOAuth.ts
  • apps/server/src/auth/SessionStore.test.ts
  • apps/server/src/auth/SessionStore.ts
  • apps/server/src/auth/http.ts
  • apps/server/src/auth/utils.ts
  • apps/server/src/cli/config.test.ts
  • apps/server/src/cli/config.ts
  • apps/server/src/cli/update.test.ts
  • apps/server/src/cli/update.ts
  • apps/server/src/cloud/bootService.ts
  • apps/server/src/cloud/pinnedRuntime.test.ts
  • apps/server/src/cloud/pinnedRuntime.ts
  • apps/server/src/cloud/releaseIndex.test.ts
  • apps/server/src/cloud/releaseIndex.ts
  • apps/server/src/cloud/selfUpdate.test.ts
  • apps/server/src/cloud/selfUpdate.ts
  • apps/server/src/config.ts
  • apps/server/src/environment/ServerEnvironment.test.ts
  • apps/server/src/environment/ServerEnvironment.ts
  • apps/server/src/environment/ServerEnvironmentLabel.ts
  • apps/server/src/lazurio/environmentLabel.test.ts
  • apps/server/src/lazurio/hostedSessionCookie.test.ts
  • apps/server/src/lazurio/hostedThreadLinks.test.ts
  • apps/server/src/lazurio/launcherLink.test.ts
  • apps/server/src/lazurio/launcherLink.ts
  • apps/server/src/server.ts
  • apps/web/src/components/chat/useAutoBalanceUpdateBanner.tsx
  • apps/web/src/components/chat/useSystemComposerBanners.tsx
  • apps/web/src/components/settings/ConnectionsSettings.tsx
  • apps/web/src/components/settings/SavedEnvironmentRows.tsx
  • apps/web/src/components/sidebar/UpdateEverythingDialog.tsx
  • apps/web/src/components/sidebar/updateEverything.logic.test.ts
  • apps/web/src/components/sidebar/updateEverything.logic.ts
  • apps/web/src/lazurio/serverUpdateOffer.test.ts
  • apps/web/src/versionSkew.test.ts
  • apps/web/src/versionSkew.ts
  • docs/operations/lazurio-fork-release.md
  • docs/operations/lazurio-overlay.md
  • docs/user/background-service.md
  • docs/user/updating.md
  • packages/client-runtime/src/lazurio/workspaceGateway.test.ts
  • packages/contracts/src/environment.ts
  • packages/shared/src/cliRelease.test.ts
  • packages/shared/src/cliRelease.ts
  • scripts/install-scripts.test.ts
  • scripts/install.ps1
  • scripts/install.sh
  • scripts/install.test.ts
  • scripts/lazurio-release-contract.test.mjs
  • scripts/lazurio-release-version.mjs
  • scripts/lazurio-release-version.test.mjs

Dále diff bran etapy 5 322f6544..bf469bb196 v souborech apps/server/src/bin.ts, apps/server/src/binCli.ts, apps/server/src/persistence/Migrations.ts, apps/server/src/persistence/Migrations/080_ScheduledTaskThreadMode.ts, packages/contracts/src/auth.ts, packages/contracts/src/environment.ts, scripts/install.sh a scripts/install.ps1, záznam bran v issue #185 a range-diff přidělených řádků proti starému main. U souborů společných více řádkům jsem posuzoval rozsah své skupiny a určené kontraktní švy.

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · bot 8dc31c93-a8be-459b-9e5d-934d2e702203
— Pablo

@agentrozjedemeai

Copy link
Copy Markdown
Collaborator

Blocking

Bez blokujícího nálezu.

Non-blocking

Bez dalších nálezů. Prošel jsem overlay v 88 různých souborech níže (120 výskytů v jednotlivých řádcích), commity c8e7aabc7c, 630666c3eb, 704fb0b632, 6649be1df7, fd1ce6eb71, ea369167dd a jejich části range-diffu vůči starému main. Změny řádků 25, 26 a 28 odpovídají uvedeným příčinám a rozhodnutím A7–A10 a A13. Zelený běh CI 42783501819 je na tomto headu; testy jsem podle zadání nespouštěl.

Prošlé soubory:

apps/server/src/auth/EnvironmentAuth.ts
apps/server/src/auth/McpOAuth.ts
apps/server/src/auth/SessionStore.ts
apps/server/src/cli/environment.ts
apps/server/src/lazurio/actingSender.test.ts
apps/server/src/lazurio/actingSender.ts
apps/server/src/lazurio/actingSenderVisibility.ts
apps/server/src/lazurio/actingSenders.test.ts
apps/server/src/lazurio/actingSenders.ts
apps/server/src/lazurio/actingSendersReplay.test.ts
apps/server/src/lazurio/actingSendersRoute.ts
apps/server/src/lazurio/agentCli.test.ts
apps/server/src/lazurio/agentCli.ts
apps/server/src/lazurio/agentCliConnection.ts
apps/server/src/lazurio/agentCliRequests.ts
apps/server/src/lazurio/agentCliSendState.ts
apps/server/src/lazurio/buddyPrompt.orchestrator.test.ts
apps/server/src/lazurio/buddyPrompt.test.ts
apps/server/src/lazurio/buddyPrompt.ts
apps/server/src/lazurio/buddySurface.testkit.ts
apps/server/src/lazurio/buddySurface.ts
apps/server/src/lazurio/buddySurfaceCli.ts
apps/server/src/lazurio/buddySurfaceDays.test.ts
apps/server/src/lazurio/buddySurfaceDays.ts
apps/server/src/lazurio/buddySurfaceGuards.test.ts
apps/server/src/lazurio/buddySurfaceGuards.ts
apps/server/src/lazurio/buddySurfaceStartup.test.ts
apps/server/src/lazurio/buddySurfaceStartup.ts
apps/server/src/lazurio/buddySurfaceThread.test.ts
apps/server/src/lazurio/buddySurfaceThread.ts
apps/server/src/lazurio/buddySurfaceThreadRoute.ts
apps/server/src/lazurio/cli.test.ts
apps/server/src/lazurio/cli.ts
apps/server/src/lazurio/overlay.ts
apps/server/src/mcp/McpInvocationContext.ts
apps/server/src/orchestration-v2/Adapters/AcpAdapterV2.test.ts
apps/server/src/orchestration-v2/ProviderTurnStartService.ts
apps/server/src/orchestration-v2/runtimeLayer.ts
apps/server/src/server.ts
apps/server/src/serverRuntimeStartup.ts
apps/server/src/ws.ts
apps/web/public/assets/avatar.webp
apps/web/src/components/ChatView.tsx
apps/web/src/components/chat/ChatBannerLane.tsx
apps/web/src/components/chat/ChatComposer.tsx
apps/web/src/components/chat/ComposerControlsBar.tsx
apps/web/src/components/chat/MessagesTimeline.tsx
apps/web/src/components/chat/QueuedRunsControl.tsx
apps/web/src/components/chat/TimelineAssistantRows.tsx
apps/web/src/components/chat/TimelineUserMessageRow.tsx
apps/web/src/components/chat/TimelineWorkEntryRow.tsx
apps/web/src/components/chat/UserMessageContextChips.tsx
apps/web/src/components/chat/timelineRowContext.ts
apps/web/src/components/chat/useComposerSend.ts
apps/web/src/components/composerContextPresentation.tsx
apps/web/src/lazurio/BuddySurface.tsx
apps/web/src/lazurio/BuddySurfacePageChip.tsx
apps/web/src/lazurio/LazurioActingSender.tsx
apps/web/src/lazurio/actingSender.test.ts
apps/web/src/lazurio/actingSender.ts
apps/web/src/lazurio/actingSenderVisibility.ts
apps/web/src/lazurio/brand/README.md
apps/web/src/lazurio/buddySurfaceControls.browser.test.tsx
apps/web/src/lazurio/buddySurfaceControls.test.ts
apps/web/src/lazurio/buddySurfaceControls.ts
apps/web/src/lazurio/buddySurfaceDayJump.browser.test.tsx
apps/web/src/lazurio/buddySurfaceFrame.test.ts
apps/web/src/lazurio/buddySurfaceFrame.ts
apps/web/src/lazurio/buddySurfacePage.test.ts
apps/web/src/lazurio/buddySurfacePage.ts
apps/web/src/lazurio/buddySurfaceProtocol.test.ts
apps/web/src/lazurio/buddySurfaceProtocol.ts
apps/web/src/lazurio/buddySurfaceQueue.browser.test.tsx
apps/web/src/lazurio/buddySurfaceRightPanel.browser.test.tsx
apps/web/src/lazurio/buddySurfaceRoute.browser.test.tsx
apps/web/src/lazurio/buddySurfaceTerminal.browser.test.tsx
apps/web/src/lazurio/buddySurfaceTheme.browser.test.tsx
apps/web/src/lazurio/buddySurfaceTimeline.browser.test.tsx
apps/web/src/lazurio/buddySurfaceTimeline.ts
apps/web/src/lazurio/chatViewPanelPresence.test.ts
apps/web/src/lazurio/useBuddyFrame.ts
apps/web/src/routes/__root.tsx
apps/web/src/routes/_chat.index.tsx
apps/web/src/routes/_chat.tsx
apps/web/src/shortcuts/chatRouteCommands.ts
docs/user/agent-cli.md
packages/contracts/src/server.ts
packages/provider-acp/src/server/adapter.ts

Agent: environment unknown · bot d3945a03-6270-4324-ada5-3cabcf1aef97
— Pablo

@agentrozjedemeai agentrozjedemeai left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verdikt: požaduji změny.

Blocking

  • Doložit podmínku A12 (issue #185): ověřte na kandidátovi, že image spustí server a že server v image i v archivech zůstane funkční při nedostupném transcribe-cpp, včetně pokusu o diktování; výsledek zapište do issue. CI image kontroluje pouze --version a soubory, nikoli start serveru. Archivový smoke test již start serveru a HTTP odpověď ověřuje, ale nesimuluje nedostupnou komponentu ani nezkouší diktování. Proto zatím není doloženo, že nedostupné diktování neshodí server, jak A12 vyžaduje.

Non-blocking

  • Existující problém se záložkou importovaného vlákna je sledován v #188.
  • Kontrola tlačítka Update, párování a uživatelského rozhraní na canary zůstává následným krokem. CI 42783501819 prošlo na tomto headu.
  • Pokrytí skupiny Shell slot a Environment browser není úplné: produkční změny byly projity, diff testovacích souborů jen výběrově. Nejde o zjištěnou vadu PR; zbývající testy je třeba dočíst při re-review příštího headu.

Pokrytí podle skupin: Steering a VCS · Agent CLI a MCP · Shell a prohlížeč · Folder, vzhled a párování · Hosting a distribuce · Buddy.

— Pablo
Agent: environment unknown · bot 48b4c66d-29ee-42d0-bf04-d6cb216f1c00

@immakermatty

Copy link
Copy Markdown
Author

Review request: head 9a4a521cdd2969f2382838f7803de92a6326cb42 (unchanged), answering the CHANGES_REQUESTED review of 2026-11-10 14:02:43 UTC point by point.

Blocking: A12 not proven. Proven now, with no code change: #185 (comment)

  • Linux x64 archive from CI run 42783501819 (artifact cli-linux-x64, head 9a4a521cdd) and an image built from git archive 9a4a521cdd with the exact arguments of the CI image step.
  • Each form ran three cases: normal, transcribe-cpp removed, and the platform's native library removed. The image also started with its default entrypoint and command.
  • In both broken cases, prepare and two transcribe calls answer 500 internal_error. / and /api/voice/status keep answering 200, and the process keeps running (archive: kill -0; image: running=true restarts=0). The server log names the missing package or library as the cause.
  • The darwin-arm64 archive is not verified; it cannot run on Linux.
  • Found along the way: when native dictation is missing, status still reports ready (upstream behaviour in apps/server/src/speech/SpeechService.ts:452-464). Separately, CI never starts the image's server and never checks that the native packages ship. Both are tracked in Fork CI never starts the release image's server or checks that dictation's native packages ship #189 and stay outside this rebuild.

Non-blocking.

  • Imported-thread tab strip: tracked in Imported thread browser sessions do not add newly bound tabs to their strip #188 and already present on the old main. No change here.
  • Update button, pairing and UI on a canary: these stay the step after the preview release (Ring 0), as the issue plans.
  • Shell slot and Environment browser test files: the head is unchanged, so please finish reading that group's test diff (aaeac29b3c 9611e5af1d 74dd87b912 ee910afa56 1e119bc6d5 a517f253a2 b12f2741b1 461098aeba) in this re-review.

What to check first: the A12 evidence in #185, then the remaining test files of the Shell slot and Environment browser group. Lazurio Fork CI is green on this head (run 42783501819).

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · bot c59bfd74-62a6-4eaa-88dd-5e19f1b3032e

@agentrozjedemeai

Copy link
Copy Markdown
Collaborator

V tomto pokusu nemohu vydat nový verdikt: nezávisle jsem nedokončil kontrolu celého overlaye (297 souborů, 47 829 přidaných řádků) a bran etapy 5; @immakermatty, prosím zajistěte dokončení kontroly zbývajících skupin a jejich testů před verdiktem na tomto headu.

Přečetl jsem runbook, rozhodnutí A12 a nové doložení v #185 a celý diff testů environmentBrowserConnection.test.ts a environmentBrowserPage.test.ts; v těchto dvou testech jsem nezjistil konkrétní závadu. Doložení A12 pokrývá image a linuxový archiv, archiv darwin-arm64 je podle záznamu neověřený. Čtyři úlohy CI 42783501819 jsou úspěšné na zadaném headu. Místní kontraktní test jsem nespustil úspěšně, protože ve worktree chybí závislost effect; ostatní předepsané místní kontroly jsem v tomto pokusu neprovedl. Předchozí REQUEST_CHANGES zůstává na GitHubu, nový verdikt jsem nepodal.

Agent: environment unknown · bot 9d17ea85-97fc-4afb-8a08-f14cd6560202
— Pablo

@immakermatty

Copy link
Copy Markdown
Author

Review request: head 9a4a521cdd2969f2382838f7803de92a6326cb42 (unchanged since the CHANGES_REQUESTED review of 2026-11-10 14:02:43 UTC). This follows the blocked attempt at 05:31:37 UTC, which tried to cover the whole overlay in one run.

Scope of this re-review (runbook docs/operations/lazurio-fork-release.md, "Review přestavby posuzuje overlay…"): the overlay was already reviewed on this exact head in six groups (lazurio-review-group comments, 2026-11-10 12:03–12:06 UTC). Five groups have no blocking finding. The head has not changed, so those group results still apply. Please compose the verdict from them plus the two items below, without re-reading the other groups:

  1. Hosting, update channel, distribution: A12. Evidence for the Linux x64 archive and the image is in Přestavba na upstream T3 Code v0.1.9 #185 (Přestavba na upstream T3 Code v0.1.9 #185 (comment)). darwin-arm64: it cannot run on a Linux host, so it is recorded in Přestavba na upstream T3 Code v0.1.9 #185 as an open condition. It must be verified on macOS from the preview release archive before stable, not before this verdict.
  2. Shell slot and Environment browser: remaining test files. Your 05:31 attempt already read environmentBrowserConnection.test.ts and environmentBrowserPage.test.ts in full and found no defect. Still to read: the rest of that group's test diff in commits aaeac29b3c 9611e5af1d 74dd87b912 ee910afa56 1e119bc6d5 a517f253a2 b12f2741b1 461098aeba.

Local tests: the worktree needs pnpm install before the contract test runs (effect is declared in apps/server/package.json:67). Lazurio Fork CI ran all four required jobs green on this head (run 42783501819).

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · bot c59bfd74-62a6-4eaa-88dd-5e19f1b3032e

@immakermatty
immakermatty requested review from agentrozjedemeai and removed request for agentrozjedemeai November 11, 2026 06:01
@agentrozjedemeai

Copy link
Copy Markdown
Collaborator

V tomto pokusu nemohu podat podložený verdikt: nedokončil jsem nezávislou kontrolu celého overlaye (297 souborů, 47 829 přidaných řádků), jeho styků s upstreamem ani všech bran etapy 5; @immakermatty, před verdiktem je třeba dokončit zbývající kontrolu těchto částí.

Ověřil jsem nezměněný head a autora, zelený běh CI, předchozí výhradu A12 a její nové doložení: image a archiv Linux x64 jsou doloženy, darwin-arm64 zůstává podmínkou před stable. Prošel jsem runbook, část rozdílů upstreamových kompatibilitních souborů a změny vybraných serverových švů, celé testy serverBrowser.test.ts a holders.test.ts; úplnou kontrolu ostatních testových souborů skupiny Shell a Environment browser ani ostatních skupin netvrdím. Místní kontraktní test prošel 51/51; cílený běh osmi serverových testovacích souborů skončil 7 prošlými soubory, jedním přeskočeným a 312 prošlými, 15 přeskočenými testy. git diff --check nad overlayem prošel. Další předepsané kontroly jsem místně neprovedl; uvedený CI běh je jejich doložením od autora. Nový verdikt jsem nepodal a předchozí REQUEST_CHANGES zůstává.

Agent: environment unknown · bot eb4f8289-21ba-4eb6-9657-e4ffc98f702a
— Pablo

@agentrozjedemeai

Copy link
Copy Markdown
Collaborator

Review nelze dokončit, protože zbývá přečíst celý diff testů skupiny Shell slot a Environment browser v osmi commitech uvedených v žádosti; reviewer může navázat na předchozí přečtení environmentBrowserConnection.test.ts a environmentBrowserPage.test.ts a na toto přečtení handlers.test.ts a LazurioNewTab.test.ts, kontraktní test zde prošel 51/51 a doklad A12 pro Linux je v #185.

Agent: environment unknown · bot 893f8471-aa66-4db7-864e-7791c0db5ab0
— Pablo

@agentrozjedemeai

Copy link
Copy Markdown
Collaborator

Zbytek re-review headu 9a4a521cdd2969f2382838f7803de92a6326cb42 jsem rozdělil mezi tři Stewardy. Tři pokusy z 05:31Z, 06:04Z a 06:05Z skončily blocked, protože se zbývající testy skupiny Shell slot and Environment browser nevešly do jednoho běhu.

Každý Steward přečte celý diff svých testových souborů z osmi commitů vaší žádosti z 06:01Z a zapíše výsledek komentářem s markerem lazurio-review-group:

  • Tests A (server): apps/server/src/lazurio/agentBrowserSession.test.ts, environmentBrowser.test.ts, threadLifecycle.test.ts, apps/server/src/orchestration-v2/Adapters/CodexAdapterV2.test.ts
  • Tests B (thread tabs): apps/server/src/lazurio/threadTabs.test.ts, threadTabsRoute.test.ts, apps/web/src/lazurio/threadTabs.browser.test.ts, threadTabs.test.ts
  • Tests C (web): apps/web/src/lazurio/LazurioEnvironmentBrowser.browser.test.tsx, LazurioNewTab.browser.test.tsx, LazurioNewTab.withoutElement.browser.test.tsx, environmentBrowser.test.ts, promptDraft.test.ts, threadServersPanel.browser.test.tsx

Soubory, které dnešní pokusy už přečetly celé (environmentBrowserConnection.test.ts, environmentBrowserPage.test.ts, serverBrowser.test.ts, holders.test.ts, handlers.test.ts, LazurioNewTab.test.ts), se znovu nečtou. Verdikt na tento head pak složí jeden Steward z komentářů šesti skupin z 2026-11-10, ze tří nových a z dokladu A12 v #185. Od vás teď nic nepotřebuji.

— Pablo
Agent: environment unknown · bot 07cea832-1d17-4bd1-8fe2-609eb4e70b1b

@agentrozjedemeai

Copy link
Copy Markdown
Collaborator

Blocking

Žádný potvrzený blokující nález v přiděleném diffu.

Non-blocking

  • agentBrowserSession.test.ts:690: test říká, že skriptový Claude startuje bez session, ale kontroluje jen příkaz a argumenty, nikoli SpawnOptions.env. Tím nedokládá, zda proměnná v prostředí procesu opravdu chybí; pro toto tvrzení by bylo potřeba ověřit i prostředí.

Přečetl jsem celý diff všech čtyř přidělených souborů v osmi určených commitech: apps/server/src/lazurio/agentBrowserSession.test.ts, apps/server/src/lazurio/environmentBrowser.test.ts, apps/server/src/lazurio/threadLifecycle.test.ts a apps/server/src/orchestration-v2/Adapters/CodexAdapterV2.test.ts. Lokálně jsem testy nespouštěl; běh CI 42783501819 je na tomto headu úspěšný.

Agent: environment unknown · bot 8dc31c93-a8be-459b-9e5d-934d2e702203 · Codex thread 01a1c9a1-8274-7883-bfa2-3277567d88c6
— Pablo

@agentrozjedemeai

Copy link
Copy Markdown
Collaborator

Blocking

Žádný doložený blokující nález v přidělených testech.

Non-blocking

  • apps/web/src/lazurio/threadTabs.browser.test.ts: případ „holdTab is idempotent for a tab the thread holds already“ volá holdTab pouze jednou, bez předem držené záložky. Ověřuje normalizovaný POST, ale nedokládá tvrzenou idempotenci klienta; pro její ověření je potřeba záložku nejprve držet nebo volání opakovat a ověřit výsledek. Serverový test opakovaný hold samostatně pokrývá.

Celý diff i celý obsah na headu jsem přečetl u těchto čtyř souborů:

  • apps/server/src/lazurio/threadTabs.test.ts
  • apps/server/src/lazurio/threadTabsRoute.test.ts
  • apps/web/src/lazurio/threadTabs.browser.test.ts
  • apps/web/src/lazurio/threadTabs.test.ts

Testy jsem lokálně nespouštěl; běh CI 42783501819 je na tomto headu úspěšný. Produkční soubory jsem podle vymezeného rozsahu samostatně nečetl, takže přímé porovnání s jejich implementací z tohoto dílčího review neplyne.

Agent: environment unknown · bot 48b4c66d-29ee-42d0-bf04-d6cb216f1c00
— Pablo

@agentrozjedemeai

Copy link
Copy Markdown
Collaborator

Blocking

V přidělených testech jsem nenašel doloženou blokující vadu ani aserci, která by tvrzené chování jen předstírala.

Non-blocking

Celé diffy i výsledný obsah všech šesti souborů jsem přečetl:

  • apps/web/src/lazurio/LazurioEnvironmentBrowser.browser.test.tsx
  • apps/web/src/lazurio/LazurioNewTab.browser.test.tsx
  • apps/web/src/lazurio/LazurioNewTab.withoutElement.browser.test.tsx
  • apps/web/src/lazurio/environmentBrowser.test.ts
  • apps/web/src/lazurio/promptDraft.test.ts
  • apps/web/src/lazurio/threadServersPanel.browser.test.tsx

V osmi zadaných commitech jde o šest nově přidaných souborů; jejich obsah se do tohoto headu dále nezměnil. Kontroloval jsem aserce a scénáře vůči popisu PR a dříve prověřeným produkčním švům skupiny; podle omezení zadání jsem nyní jiné soubory znovu nečetl. Testy jsem lokálně nespouštěl; CI 42783501819 je na tomto headu zelené.

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · bot 22dde332-171b-4cd7-8380-644bdc815739
— Pablo

@agentrozjedemeai agentrozjedemeai left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verdikt: schvaluji.

Blocking

Předchozí výhrada k A12 je pro image a archiv Linux x64 doložena: při chybějícím balíčku i nativní knihovně pokus o diktování skončil chybou, ale server zůstal funkční. Doklad a postup. Archiv darwin-arm64 zůstává neověřený; jeho ověření na macOS je podle rozhodnutí vlastníka podmínkou před stable.

Non-blocking

Zbývající testy skupiny Shell a Environment browser byly dočteny ve skupinách A, B a C; jejich poznámky k testům jsou v těchto komentářích. Původní výsledky ostatních skupin jsou odkázány v předchozím review. CI 42783501819 prošlo na tomto headu. Kontrola Update, párování a UI na canary zůstává následným krokem.

— Pablo

@immakermatty

Copy link
Copy Markdown
Author

Superseded by #192. Upstream released v0.1.9 during this rebuild, so the rebuild moved straight to it (decision N, #185 (comment)). #192 is this PR's approved head 9a4a521cdd2969f2382838f7803de92a6326cb42 cherry-picked onto v0.1.9 row by row; its review is limited to the range-diff against 9a4a521cdd and the gates v0.1.8 → v0.1.9 touches. The branch lazurio/rebuild-v0.1.8 stays as the approved basis.

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · bot c59bfd74-62a6-4eaa-88dd-5e19f1b3032e

immakermatty added a commit that referenced this pull request Nov 18, 2026
The distribution's files on the new base, upstream T3 Code v0.1.10
(7d32075), last in the stack: CI,
the CLI archive, release and upstream watch workflows, the image, the
issue form, README, SECURITY.md, the runbook, the overlay spec, the
contract test, the release version check and the rebuild's skill. They
are main's files, made current for v0.1.10 (#213). Main's
base is v0.1.9 (#185); the notes for v0.1.4 to v0.1.9
below are kept from the earlier rebuilds.

On v0.1.4:

- The allowlist gains five files: chat/ThreadServersPanel.tsx, where a
  click on a thread's server opens it in the Environment browser (row 9);
  sidebar/UpdateEverythingDialog.tsx and updateEverything.logic.test.ts,
  for the per-server target and the continuation gate of v0.1.4's update
  dialog (row 4); upstream's installer test install.test.ts, whose fixture
  needs upstream's repository named (row 4); and cli/environment.ts, whose
  settings take Buddy's linked-Environments guard (row 25).
  ServerEnvironment.test.ts keeps the update-check guard (row 4).
- The contract test's pins follow the seams that moved: upstream deleted
  LegacySidebar.tsx (pingdotgg#21039), so the shell slot's column
  head is pinned in the thread sidebar only; the sidebar reads
  useDelegatedUnderParent before the managed check; the empty panel and
  Nová karta carry the workspace focus default; the MCP session issue
  calls mcpClientScopes directly; an agent command's scope drops the
  session's web origin so its thread links stay t3-thread:// links; the
  Buddy composer hook takes only the environment, since v0.1.4's resting
  composer has no strip of its own; the timeline has no paint-only gate
  (pingdotgg#25787); the steer guard returns through
  stopRunForQueuedCommand and also holds a delegated task's completion
  wake; the Servers panel's click opens the Environment browser; and
  Buddy's server settings layer turns linked Environments off.
- Rows 30, 32 and 33, which main carried as commits after row 31, now
  sit in their rows; row 28's addenda are back in rows 7, 23 and 25.
  Upstream renamed the lint rule react-effect-budget to
  t3code/no-unreasoned-state-sync (pingdotgg#26161).
- The skill's inventory groups cover rows 23 to 33.
- Tests, fixtures and docs of rows 9, 10, 21, 23, 25, 26 and 27 name
  only fictional people and hosts (Alena, Bob, example-person,
  vm-0x.example.lazurio.io), since the repository is public.

On v0.1.5:

- CI and the contract test pin v0.1.5 and build 0.1.5-lazurio.0; the
  issue form's version example is 0.1.5-lazurio.1. Node 26.12.1 and pnpm
  12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy.
- The Linux CLI archive now ships lib/libatomic.so.1 and patchelf sets
  t3's RUNPATH to it (pingdotgg#26912, pingdotgg#26932), so
  lazurio-cli-archives.yml installs patchelf before the build, the way
  upstream's release-desktop.yml does; the contract test pins the order.
- useUpdateEverything.ts leaves the allowlist: row 4 now keeps a
  server's advertised release out of waitForNpm in
  updateEverything.logic.ts (pingdotgg#26917), and the contract
  test pins that seam there. The fixed test gate is unchanged, and every
  gated path exists at v0.1.5.
- The contract test's pairing pins follow the constants that knip made
  module-private (upstream's pre-commit hook runs knip:check since
  pingdotgg#26167).
- The runbook's Overlay table describes every row on v0.1.5, the Cílový
  stack names each row's new commit, the swap step names the workflows
  to disable after the swap from the v0.1.3 base (agent-context-budget.yml,
  mobile-fingerprint-label.yml; v0.1.5 adds none), and stage 3 and the
  skill say to replay with --no-verify and run knip over the finished
  stack.

On v0.1.6:

- CI and the contract test pin v0.1.6 and build 0.1.6-lazurio.0; the
  issue form's version example is 0.1.6-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
- The allowlist is unchanged. Its comments say why ServerEnvironment.ts
  and server.ts offer and build no triage on a Lazurio Environment
  (row 15, #147), why ws.ts runs no ChatGPT handoff there
  and the web starts none through a Lazurio primary (row 18,
  #145), that useComposerSend.ts counts a prompt toward
  upstream's star request (pingdotgg#27832) only outside a Lazurio
  Environment (row 16), and that no update waits on npm since
  pingdotgg#27847 (row 4).
- The contract test pins those seams: the triage guard and its one
  construction, the star prompt's check and its one call, the handoff
  route, reconnectProfile and the web's routing, and on Buddy's surface
  the inline mask over useThreadLifecycle's attentionNow and workNow,
  every line of it (React Compiler, #135), the items'
  counts in useThreadLifecycle.tsx and its one caller, the promise
  ChatView hands Nová karta for a side chat (row 13), and that Buddy's
  surface offers no side chat (row 25). It also follows
  the seams upstream moved: no waitForNpm left in the update dialog's
  logic, the palette's addProjectAction, the sidebar's pickable project
  groups (pingdotgg#26154), and an embedded side chat
  (pingdotgg#26901) without thread tabs, terminal drawers or the
  right panel. Claude's mcp-elicitation requests and the agent scope's
  kill are covered by rows 30 and 8's own tests.
- The runbook's Overlay table describes every row on v0.1.6, the Cílový
  stack names each row's new commit and the files rows 13, 15, 16 and 18
  now change, and the swap step adds mobile-eas-preview-fork.yml to the
  workflows to disable after the swap. The runbook and the skill say to
  address a fix written over the finished stack to the row that added
  the place it changes.

On v0.1.7:

- CI and the contract test pin v0.1.7 and build 0.1.7-lazurio.0; the
  issue form's version example is 0.1.7-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
  v0.1.7 adds no workflow, so the swap step's list is unchanged.
- The allowlist gains toolkits/preview/handlers.ts and its test: since
  v0.1.7 preview_open takes a dev-server target (pingdotgg#28027),
  and upstream's handler answered an open with a target with the
  navigate result alone; row 10 keeps the open answer underneath, so the
  Environment browser's view stays. The fixed test gate is unchanged.
- The contract test follows the seams that moved: the settings writer
  takes the client's patch for the managed policy
  (updateAndPersistSettings, pingdotgg#27197), Hermes's runtime
  notes come from the active session setup, the MCP caller's webOrigin
  is now hostedAppUrl, the steer guard's waitsOnPendingRequest also
  holds a delegated task's question (pingdotgg#29909), and the
  ACP adapter filters T3's options through a flatMap.
- For row 30 the allowlist gains apps/web's components/ChatView.logic.ts
  and its test and components/chat/composerCommandKey.ts,
  client-runtime's state/composerDispatch.ts and its test, and
  contracts' orchestrationV2.ts: eight files with the two above. The
  contract test pins that the web keeps auto input auto while the run is
  set up; that /compact and /logout wait for no turn; that a running
  update takes the thread lock on its provider turn's first report or
  while a follow-up waits, then checks again under the lock; and that
  each follow-up gets one promotion, so a held one, one already promoted
  and a refused one stay queued without holding back the next.
- Stage 3's checkout command names the release version check's script
  and test (#165), which the v0.1.6 runbook left out.
- The runbook's Overlay table describes every row on v0.1.7, and the
  Cílový stack names each row's new commit. Main's Cílový stack still
  named older hashes from row 10 on, so the runbook and the skill now say
  to take each row's commit from main's log by subject. The runbook also
  records the Effect 4.1.2 test recipe (NodeCrypto beside NodeServices,
  ManagedPolicy.layerTest()) and that the overlay's settings writes go
  through updateSettingsWith, so the managed policy vets them.
- The runbook records what the independent check of this rebuild found:
  Codex 0.166.0, T3's managed runtime since v0.1.7, still has
  default_mode_request_user_input off by default (row 22); mcp-client
  sessions get hosted thread links on the external origin (row 20);
  upstream's star prompt now stars through the Environment's account
  (row 16); the policy lock reads the macOS and Windows sources too
  (row 18); two upstream policy paths in the update flow do not follow
  row 4's target and are offered upstream; row 30's refused promotion,
  /goal and cold-start steer; and row 33's steer page block. The overlay
  CLI tests build auth on the test managed policy.

On v0.1.8:

- CI and the contract test pin v0.1.8 and build 0.1.8-lazurio.0; the
  issue form's version example is 0.1.8-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy, whose contact is now
  security@t3.codes.
- The allowlist is unchanged. v0.1.8 adds no workflow, so the swap
  step's list is unchanged. Upstream's release-desktop.yml can now defer
  the macOS CLI's notarization with --notary-submission-file;
  lazurio-cli-archives.yml signs ad hoc, passes no such file and is
  unchanged.
- The contract test follows the seams that moved: the sidebar control
  takes showSidebar; the composer controls bar's hooks end with the
  model pick (pingdotgg#31739) and Buddy's controls return after
  them; an offered prompt suggestion comes before Buddy's placeholder
  (pingdotgg#28047); and a fresh session after /clear
  (pingdotgg#30325) never steers, in the web's dispatch mode and
  in the server's steer and promotion guards. Two new pins keep the
  Buddy surface's hides of upstream's new entries: "Use in another app"
  (decision A8) and /clear's fresh session (decision A7).
- The runbook's Overlay table describes every row on v0.1.8, the Cílový
  stack names each row's new commit and files (viewAddressCases.ts in
  rows 9 and 10), and row 30's text no longer compares
  waitsOnPendingRequest with snooze, which since v0.1.8 ignores a pending
  user_input. The runbook records this rebuild's conflicts and that a
  test the rebuild adds belongs in the row's own test file or under
  apps/*/src/lazurio/, since an upstream test file off the allowlist
  fails fork CI.

On v0.1.9:

- CI and the contract test pin v0.1.9 and build 0.1.9-lazurio.0; the
  issue form's version example is 0.1.9-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. Upstream left
  SECURITY.md unchanged, so its upstream section still equals the tag's
  policy.
- The allowlist is unchanged. The contract test's seams are unchanged
  apart from one new pin, and the tag and SHA pins move. The stack replays the approved v0.1.8 candidate
  (#187) on v0.1.9, and rows 4, 9, 15, 28 and 30 name
  their adaptations in their own messages.
- v0.1.9 adds mobile-dev-client.yml (push to main, pull_request on its
  own file and scripts/mobile-native-client.ts, workflow_dispatch); both its jobs run only in
  pingdotgg/t3code, and the swap step adds it to the workflows to
  disable after the swap. The changed ci.yml and four mobile workflows
  stay disabled.
- The runbook's Overlay table describes every row on v0.1.9, the
  Cílový stack names each row's new commit, and the runbook records
  this rebuild's conflicts and decisions. Upstream's new screen reader
  announcements (pingdotgg#33900) are capped at Buddy's messages on Buddy's
  surface, so a screen reader never hears T3's steps there (row 28);
  the contract test pins that cap in MessagesTimeline.tsx.

On v0.1.10:

- CI and the contract test pin v0.1.10 and build 0.1.10-lazurio.0; the
  issue form's version example is 0.1.10-lazurio.1. Upstream moved to
  Node 26.13.1 (pnpm 12.14.0 is unchanged), so CI, the release and the
  image pin Node 26.13.1 and node:26.13.1-bookworm by its index digest.
  Upstream left SECURITY.md unchanged, so its upstream section still
  equals the tag's policy; this row adds the fork's section to it.
- The allowlist drops branding.ts, ChatView.logic.ts and its test,
  composerCommandKey.ts and composerDispatch.ts and its test, which the
  overlay no longer changes: upstream now picks the stage label in
  branding.logic.ts, and it steers a follow-up sent before the provider
  turn started (pingdotgg#34581). Row 30 now turns an auto send
  made then into that deferred steer in Orchestrator.ts and marks it
  automatic on the queued run, so orchestrationV2.ts stays
  (#170). It adds sidebar/updateEverythingRun.tsx and its
  test, where row 4's Retry compares a Lazurio release's whole version,
  and three new upstream tests: SidebarUpdatePill.browser.test.tsx, whose rows carry
  row 4's per-row target; main.test.ts, whose stand-in window carries
  the address the prompt link capture reads (row 6); and binCli.test.ts,
  which reads row 21's `t3 thread list --json` with its total. The guard
  passes both ways on the candidate.
- The contract test follows the seams upstream moved: the launcher path
  now comes from cloud/pinnedRuntime.ts, the build stamps the page title
  from the stage label (pingdotgg#18442, and no release workflow
  sets VITE_HOSTED_APP_CHANNEL), ACP runtime instructions are one flag
  (sendRuntimeInstructions), the ACP adapter also resets unset options
  (pingdotgg#35199, held back on Buddy's instance too), provider
  hydration reads the database config (pingdotgg#34877), a
  natively resumed thread sends its unsent message
  (pingdotgg#36526), a failed send gives back the snapshot's
  draftText (pingdotgg#33124), a linked Environment's sender names
  it (pingdotgg#34721), an expandable work row's chevron sits
  between the acting-sender mark and the time (pingdotgg#35549),
  and the collapsed composer previews the prompt (pingdotgg#22148).
  Row 30's checks now pin that the one promote-to-steer is upstream's
  deferred steer, behind the pending-request guard that clears its
  steerWhenReadyRunId and steerWhenReadyIntent; the conditions under
  which an auto send in the gap becomes that steer, through
  resolveMessageDispatchIntent and the adapter's steering or
  interrupt-and-restart; and the delivery check that lets such a steer in
  only where the policy steers it then, by the session's capabilities.
- v0.1.10 adds issue-vouch.yml (issues, push to main on VOUCHED.td) and
  pr-limits.yml (pull_request_target and a daily schedule at 05:23 UTC;
  it labels, comments on and closes pull requests, dry-run without
  PR_LIMITS_ENFORCE). Both run on ubuntu-24.04 in the fork too, so the
  swap step disables them right after the swap. The swap push itself
  starts issue-vouch.yml, since it adds the workflow and VOUCHED.td, so
  the step first cancels that run and then removes any vouch label it
  gave an open issue.
- The Overlay table gains rows 35 to 37 for #214 and #216, and the
  Cílový stack names their commits on main and their files. Rows 4, 15,
  21 and 30 record the fixes from the candidate's independent check
  (#222); the rest of the table is brought up to v0.1.10
  after the release (stage 9). The runbook's "Z přestavby na v0.1.10"
  records the conflicts, the hand adaptations and those fixes, numbering
  rows as the table does, and names the replayed main (faae02a, stable
  0.1.9-lazurio.2: 0.1.9-lazurio.1 at 388b772 with #214 and #216).
- Main's #214, #216 and #220 additions to CI, the contract test and the
  runbook are carried unchanged; #216's narrow-rail pin follows row 36's
  `hidden` adaptation. A new contract pin holds row 35's hand-placed
  coordinator change: ThreadNotificationCoordinator.tsx reads hidden
  threads three times, always as listHiddenThreadKeysAtom, so Buddy's
  project's threads never sound, toast or notify.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
immakermatty added a commit that referenced this pull request Nov 18, 2026
The distribution's files on the new base, upstream T3 Code v0.1.10
(7d32075), last in the stack: CI,
the CLI archive, release and upstream watch workflows, the image, the
issue form, README, SECURITY.md, the runbook, the overlay spec, the
contract test, the release version check and the rebuild's skill. They
are main's files, made current for v0.1.10 (#213). Main's
base is v0.1.9 (#185); the notes for v0.1.4 to v0.1.9
below are kept from the earlier rebuilds.

On v0.1.4:

- The allowlist gains five files: chat/ThreadServersPanel.tsx, where a
  click on a thread's server opens it in the Environment browser (row 9);
  sidebar/UpdateEverythingDialog.tsx and updateEverything.logic.test.ts,
  for the per-server target and the continuation gate of v0.1.4's update
  dialog (row 4); upstream's installer test install.test.ts, whose fixture
  needs upstream's repository named (row 4); and cli/environment.ts, whose
  settings take Buddy's linked-Environments guard (row 25).
  ServerEnvironment.test.ts keeps the update-check guard (row 4).
- The contract test's pins follow the seams that moved: upstream deleted
  LegacySidebar.tsx (pingdotgg#21039), so the shell slot's column
  head is pinned in the thread sidebar only; the sidebar reads
  useDelegatedUnderParent before the managed check; the empty panel and
  Nová karta carry the workspace focus default; the MCP session issue
  calls mcpClientScopes directly; an agent command's scope drops the
  session's web origin so its thread links stay t3-thread:// links; the
  Buddy composer hook takes only the environment, since v0.1.4's resting
  composer has no strip of its own; the timeline has no paint-only gate
  (pingdotgg#25787); the steer guard returns through
  stopRunForQueuedCommand and also holds a delegated task's completion
  wake; the Servers panel's click opens the Environment browser; and
  Buddy's server settings layer turns linked Environments off.
- Rows 30, 32 and 33, which main carried as commits after row 31, now
  sit in their rows; row 28's addenda are back in rows 7, 23 and 25.
  Upstream renamed the lint rule react-effect-budget to
  t3code/no-unreasoned-state-sync (pingdotgg#26161).
- The skill's inventory groups cover rows 23 to 33.
- Tests, fixtures and docs of rows 9, 10, 21, 23, 25, 26 and 27 name
  only fictional people and hosts (Alena, Bob, example-person,
  vm-0x.example.lazurio.io), since the repository is public.

On v0.1.5:

- CI and the contract test pin v0.1.5 and build 0.1.5-lazurio.0; the
  issue form's version example is 0.1.5-lazurio.1. Node 26.12.1 and pnpm
  12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy.
- The Linux CLI archive now ships lib/libatomic.so.1 and patchelf sets
  t3's RUNPATH to it (pingdotgg#26912, pingdotgg#26932), so
  lazurio-cli-archives.yml installs patchelf before the build, the way
  upstream's release-desktop.yml does; the contract test pins the order.
- useUpdateEverything.ts leaves the allowlist: row 4 now keeps a
  server's advertised release out of waitForNpm in
  updateEverything.logic.ts (pingdotgg#26917), and the contract
  test pins that seam there. The fixed test gate is unchanged, and every
  gated path exists at v0.1.5.
- The contract test's pairing pins follow the constants that knip made
  module-private (upstream's pre-commit hook runs knip:check since
  pingdotgg#26167).
- The runbook's Overlay table describes every row on v0.1.5, the Cílový
  stack names each row's new commit, the swap step names the workflows
  to disable after the swap from the v0.1.3 base (agent-context-budget.yml,
  mobile-fingerprint-label.yml; v0.1.5 adds none), and stage 3 and the
  skill say to replay with --no-verify and run knip over the finished
  stack.

On v0.1.6:

- CI and the contract test pin v0.1.6 and build 0.1.6-lazurio.0; the
  issue form's version example is 0.1.6-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
- The allowlist is unchanged. Its comments say why ServerEnvironment.ts
  and server.ts offer and build no triage on a Lazurio Environment
  (row 15, #147), why ws.ts runs no ChatGPT handoff there
  and the web starts none through a Lazurio primary (row 18,
  #145), that useComposerSend.ts counts a prompt toward
  upstream's star request (pingdotgg#27832) only outside a Lazurio
  Environment (row 16), and that no update waits on npm since
  pingdotgg#27847 (row 4).
- The contract test pins those seams: the triage guard and its one
  construction, the star prompt's check and its one call, the handoff
  route, reconnectProfile and the web's routing, and on Buddy's surface
  the inline mask over useThreadLifecycle's attentionNow and workNow,
  every line of it (React Compiler, #135), the items'
  counts in useThreadLifecycle.tsx and its one caller, the promise
  ChatView hands Nová karta for a side chat (row 13), and that Buddy's
  surface offers no side chat (row 25). It also follows
  the seams upstream moved: no waitForNpm left in the update dialog's
  logic, the palette's addProjectAction, the sidebar's pickable project
  groups (pingdotgg#26154), and an embedded side chat
  (pingdotgg#26901) without thread tabs, terminal drawers or the
  right panel. Claude's mcp-elicitation requests and the agent scope's
  kill are covered by rows 30 and 8's own tests.
- The runbook's Overlay table describes every row on v0.1.6, the Cílový
  stack names each row's new commit and the files rows 13, 15, 16 and 18
  now change, and the swap step adds mobile-eas-preview-fork.yml to the
  workflows to disable after the swap. The runbook and the skill say to
  address a fix written over the finished stack to the row that added
  the place it changes.

On v0.1.7:

- CI and the contract test pin v0.1.7 and build 0.1.7-lazurio.0; the
  issue form's version example is 0.1.7-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
  v0.1.7 adds no workflow, so the swap step's list is unchanged.
- The allowlist gains toolkits/preview/handlers.ts and its test: since
  v0.1.7 preview_open takes a dev-server target (pingdotgg#28027),
  and upstream's handler answered an open with a target with the
  navigate result alone; row 10 keeps the open answer underneath, so the
  Environment browser's view stays. The fixed test gate is unchanged.
- The contract test follows the seams that moved: the settings writer
  takes the client's patch for the managed policy
  (updateAndPersistSettings, pingdotgg#27197), Hermes's runtime
  notes come from the active session setup, the MCP caller's webOrigin
  is now hostedAppUrl, the steer guard's waitsOnPendingRequest also
  holds a delegated task's question (pingdotgg#29909), and the
  ACP adapter filters T3's options through a flatMap.
- For row 30 the allowlist gains apps/web's components/ChatView.logic.ts
  and its test and components/chat/composerCommandKey.ts,
  client-runtime's state/composerDispatch.ts and its test, and
  contracts' orchestrationV2.ts: eight files with the two above. The
  contract test pins that the web keeps auto input auto while the run is
  set up; that /compact and /logout wait for no turn; that a running
  update takes the thread lock on its provider turn's first report or
  while a follow-up waits, then checks again under the lock; and that
  each follow-up gets one promotion, so a held one, one already promoted
  and a refused one stay queued without holding back the next.
- Stage 3's checkout command names the release version check's script
  and test (#165), which the v0.1.6 runbook left out.
- The runbook's Overlay table describes every row on v0.1.7, and the
  Cílový stack names each row's new commit. Main's Cílový stack still
  named older hashes from row 10 on, so the runbook and the skill now say
  to take each row's commit from main's log by subject. The runbook also
  records the Effect 4.1.2 test recipe (NodeCrypto beside NodeServices,
  ManagedPolicy.layerTest()) and that the overlay's settings writes go
  through updateSettingsWith, so the managed policy vets them.
- The runbook records what the independent check of this rebuild found:
  Codex 0.166.0, T3's managed runtime since v0.1.7, still has
  default_mode_request_user_input off by default (row 22); mcp-client
  sessions get hosted thread links on the external origin (row 20);
  upstream's star prompt now stars through the Environment's account
  (row 16); the policy lock reads the macOS and Windows sources too
  (row 18); two upstream policy paths in the update flow do not follow
  row 4's target and are offered upstream; row 30's refused promotion,
  /goal and cold-start steer; and row 33's steer page block. The overlay
  CLI tests build auth on the test managed policy.

On v0.1.8:

- CI and the contract test pin v0.1.8 and build 0.1.8-lazurio.0; the
  issue form's version example is 0.1.8-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy, whose contact is now
  security@t3.codes.
- The allowlist is unchanged. v0.1.8 adds no workflow, so the swap
  step's list is unchanged. Upstream's release-desktop.yml can now defer
  the macOS CLI's notarization with --notary-submission-file;
  lazurio-cli-archives.yml signs ad hoc, passes no such file and is
  unchanged.
- The contract test follows the seams that moved: the sidebar control
  takes showSidebar; the composer controls bar's hooks end with the
  model pick (pingdotgg#31739) and Buddy's controls return after
  them; an offered prompt suggestion comes before Buddy's placeholder
  (pingdotgg#28047); and a fresh session after /clear
  (pingdotgg#30325) never steers, in the web's dispatch mode and
  in the server's steer and promotion guards. Two new pins keep the
  Buddy surface's hides of upstream's new entries: "Use in another app"
  (decision A8) and /clear's fresh session (decision A7).
- The runbook's Overlay table describes every row on v0.1.8, the Cílový
  stack names each row's new commit and files (viewAddressCases.ts in
  rows 9 and 10), and row 30's text no longer compares
  waitsOnPendingRequest with snooze, which since v0.1.8 ignores a pending
  user_input. The runbook records this rebuild's conflicts and that a
  test the rebuild adds belongs in the row's own test file or under
  apps/*/src/lazurio/, since an upstream test file off the allowlist
  fails fork CI.

On v0.1.9:

- CI and the contract test pin v0.1.9 and build 0.1.9-lazurio.0; the
  issue form's version example is 0.1.9-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. Upstream left
  SECURITY.md unchanged, so its upstream section still equals the tag's
  policy.
- The allowlist is unchanged. The contract test's seams are unchanged
  apart from one new pin, and the tag and SHA pins move. The stack replays the approved v0.1.8 candidate
  (#187) on v0.1.9, and rows 4, 9, 15, 28 and 30 name
  their adaptations in their own messages.
- v0.1.9 adds mobile-dev-client.yml (push to main, pull_request on its
  own file and scripts/mobile-native-client.ts, workflow_dispatch); both its jobs run only in
  pingdotgg/t3code, and the swap step adds it to the workflows to
  disable after the swap. The changed ci.yml and four mobile workflows
  stay disabled.
- The runbook's Overlay table describes every row on v0.1.9, the
  Cílový stack names each row's new commit, and the runbook records
  this rebuild's conflicts and decisions. Upstream's new screen reader
  announcements (pingdotgg#33900) are capped at Buddy's messages on Buddy's
  surface, so a screen reader never hears T3's steps there (row 28);
  the contract test pins that cap in MessagesTimeline.tsx.

On v0.1.10:

- CI and the contract test pin v0.1.10 and build 0.1.10-lazurio.0; the
  issue form's version example is 0.1.10-lazurio.1. Upstream moved to
  Node 26.13.1 (pnpm 12.14.0 is unchanged), so CI, the release and the
  image pin Node 26.13.1 and node:26.13.1-bookworm by its index digest.
  Upstream left SECURITY.md unchanged, so its upstream section still
  equals the tag's policy; this row adds the fork's section to it.
- The allowlist drops branding.ts, ChatView.logic.ts and its test,
  composerCommandKey.ts and composerDispatch.ts and its test, which the
  overlay no longer changes: upstream now picks the stage label in
  branding.logic.ts, and it steers a follow-up sent before the provider
  turn started (pingdotgg#34581). Row 30 now turns an auto send
  made then into that deferred steer in Orchestrator.ts and marks it
  automatic on the queued run, so orchestrationV2.ts stays
  (#170). It adds sidebar/updateEverythingRun.tsx and its
  test, where row 4's Retry compares a Lazurio release's whole version,
  and three new upstream tests: SidebarUpdatePill.browser.test.tsx, whose rows carry
  row 4's per-row target; main.test.ts, whose stand-in window carries
  the address the prompt link capture reads (row 6); and binCli.test.ts,
  which reads row 21's `t3 thread list --json` with its total. The guard
  passes both ways on the candidate.
- The contract test follows the seams upstream moved: the launcher path
  now comes from cloud/pinnedRuntime.ts, the build stamps the page title
  from the stage label (pingdotgg#18442, and no release workflow
  sets VITE_HOSTED_APP_CHANNEL), ACP runtime instructions are one flag
  (sendRuntimeInstructions), the ACP adapter also resets unset options
  (pingdotgg#35199, held back on Buddy's instance too), provider
  hydration reads the database config (pingdotgg#34877), a
  natively resumed thread sends its unsent message
  (pingdotgg#36526), a failed send gives back the snapshot's
  draftText (pingdotgg#33124), a linked Environment's sender names
  it (pingdotgg#34721), an expandable work row's chevron sits
  between the acting-sender mark and the time (pingdotgg#35549),
  and the collapsed composer previews the prompt (pingdotgg#22148).
  Row 30's checks now pin that the one promote-to-steer is upstream's
  deferred steer, behind the pending-request guard that clears its
  steerWhenReadyRunId and steerWhenReadyIntent; the conditions under
  which an auto send in the gap becomes that steer, through
  resolveMessageDispatchIntent and the adapter's steering or
  interrupt-and-restart; and the delivery check that lets such a steer in
  only where the policy steers it then, by the session's capabilities.
- v0.1.10 adds issue-vouch.yml (issues, push to main on VOUCHED.td) and
  pr-limits.yml (pull_request_target and a daily schedule at 05:23 UTC;
  it labels, comments on and closes pull requests, dry-run without
  PR_LIMITS_ENFORCE). Both run on ubuntu-24.04 in the fork too, so the
  swap step disables them right after the swap. The swap push itself
  starts issue-vouch.yml, since it adds the workflow and VOUCHED.td, so
  the step first cancels that run and then removes any vouch label it
  gave an open issue.
- The Overlay table gains rows 35 to 37 for #214 and #216, and the
  Cílový stack names their commits on main and their files. Rows 4, 15,
  21 and 30 record the fixes from the candidate's independent check
  (#222); the rest of the table is brought up to v0.1.10
  after the release (stage 9). The runbook's "Z přestavby na v0.1.10"
  records the conflicts, the hand adaptations and those fixes, numbering
  rows as the table does, and names the replayed main (faae02a, stable
  0.1.9-lazurio.2: 0.1.9-lazurio.1 at 388b772 with #214 and #216).
- Main's #214, #216 and #220 additions to CI, the contract test and the
  runbook are carried unchanged; #216's narrow-rail pin follows row 36's
  `hidden` adaptation. A new contract pin holds row 35's hand-placed
  coordinator change: ThreadNotificationCoordinator.tsx reads hidden
  threads three times, always as listHiddenThreadKeysAtom, so Buddy's
  project's threads never sound, toast or notify.
- The review of the candidate at 50a5004 (#222) adds to
  the runbook: the contract inventory names orchestrationV2.ts with
  steerWhenReadyIntent only; rows 24 and 30 record the recorded
  followWakes and the auto steer that a question puts first in the
  queue; the F50 gate names holders.vectors.test.ts and the vendored
  Platform v0.1.22 vectors; the check that ~/.local/bin/t3 points to the
  new version reads both forms of the launcher, a symlink and since
  v0.1.10 the script posixLauncherScript writes; and the update channel
  and its procedure describe the launcher protocol's move from 3 to 4,
  which an Update from 0.1.9 passes while the 0.1.9 launcher stays until
  a local update or service install restarts the service. The contract
  test pins the copied release and the vectors' runner.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
immakermatty added a commit that referenced this pull request Nov 18, 2026
The distribution's files on the new base, upstream T3 Code v0.1.10
(7d32075), last in the stack: CI,
the CLI archive, release and upstream watch workflows, the image, the
issue form, README, SECURITY.md, the runbook, the overlay spec, the
contract test, the release version check and the rebuild's skill. They
are main's files, made current for v0.1.10 (#213). Main's
base is v0.1.9 (#185); the notes for v0.1.4 to v0.1.9
below are kept from the earlier rebuilds.

On v0.1.4:

- The allowlist gains five files: chat/ThreadServersPanel.tsx, where a
  click on a thread's server opens it in the Environment browser (row 9);
  sidebar/UpdateEverythingDialog.tsx and updateEverything.logic.test.ts,
  for the per-server target and the continuation gate of v0.1.4's update
  dialog (row 4); upstream's installer test install.test.ts, whose fixture
  needs upstream's repository named (row 4); and cli/environment.ts, whose
  settings take Buddy's linked-Environments guard (row 25).
  ServerEnvironment.test.ts keeps the update-check guard (row 4).
- The contract test's pins follow the seams that moved: upstream deleted
  LegacySidebar.tsx (pingdotgg#21039), so the shell slot's column
  head is pinned in the thread sidebar only; the sidebar reads
  useDelegatedUnderParent before the managed check; the empty panel and
  Nová karta carry the workspace focus default; the MCP session issue
  calls mcpClientScopes directly; an agent command's scope drops the
  session's web origin so its thread links stay t3-thread:// links; the
  Buddy composer hook takes only the environment, since v0.1.4's resting
  composer has no strip of its own; the timeline has no paint-only gate
  (pingdotgg#25787); the steer guard returns through
  stopRunForQueuedCommand and also holds a delegated task's completion
  wake; the Servers panel's click opens the Environment browser; and
  Buddy's server settings layer turns linked Environments off.
- Rows 30, 32 and 33, which main carried as commits after row 31, now
  sit in their rows; row 28's addenda are back in rows 7, 23 and 25.
  Upstream renamed the lint rule react-effect-budget to
  t3code/no-unreasoned-state-sync (pingdotgg#26161).
- The skill's inventory groups cover rows 23 to 33.
- Tests, fixtures and docs of rows 9, 10, 21, 23, 25, 26 and 27 name
  only fictional people and hosts (Alena, Bob, example-person,
  vm-0x.example.lazurio.io), since the repository is public.

On v0.1.5:

- CI and the contract test pin v0.1.5 and build 0.1.5-lazurio.0; the
  issue form's version example is 0.1.5-lazurio.1. Node 26.12.1 and pnpm
  12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy.
- The Linux CLI archive now ships lib/libatomic.so.1 and patchelf sets
  t3's RUNPATH to it (pingdotgg#26912, pingdotgg#26932), so
  lazurio-cli-archives.yml installs patchelf before the build, the way
  upstream's release-desktop.yml does; the contract test pins the order.
- useUpdateEverything.ts leaves the allowlist: row 4 now keeps a
  server's advertised release out of waitForNpm in
  updateEverything.logic.ts (pingdotgg#26917), and the contract
  test pins that seam there. The fixed test gate is unchanged, and every
  gated path exists at v0.1.5.
- The contract test's pairing pins follow the constants that knip made
  module-private (upstream's pre-commit hook runs knip:check since
  pingdotgg#26167).
- The runbook's Overlay table describes every row on v0.1.5, the Cílový
  stack names each row's new commit, the swap step names the workflows
  to disable after the swap from the v0.1.3 base (agent-context-budget.yml,
  mobile-fingerprint-label.yml; v0.1.5 adds none), and stage 3 and the
  skill say to replay with --no-verify and run knip over the finished
  stack.

On v0.1.6:

- CI and the contract test pin v0.1.6 and build 0.1.6-lazurio.0; the
  issue form's version example is 0.1.6-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
- The allowlist is unchanged. Its comments say why ServerEnvironment.ts
  and server.ts offer and build no triage on a Lazurio Environment
  (row 15, #147), why ws.ts runs no ChatGPT handoff there
  and the web starts none through a Lazurio primary (row 18,
  #145), that useComposerSend.ts counts a prompt toward
  upstream's star request (pingdotgg#27832) only outside a Lazurio
  Environment (row 16), and that no update waits on npm since
  pingdotgg#27847 (row 4).
- The contract test pins those seams: the triage guard and its one
  construction, the star prompt's check and its one call, the handoff
  route, reconnectProfile and the web's routing, and on Buddy's surface
  the inline mask over useThreadLifecycle's attentionNow and workNow,
  every line of it (React Compiler, #135), the items'
  counts in useThreadLifecycle.tsx and its one caller, the promise
  ChatView hands Nová karta for a side chat (row 13), and that Buddy's
  surface offers no side chat (row 25). It also follows
  the seams upstream moved: no waitForNpm left in the update dialog's
  logic, the palette's addProjectAction, the sidebar's pickable project
  groups (pingdotgg#26154), and an embedded side chat
  (pingdotgg#26901) without thread tabs, terminal drawers or the
  right panel. Claude's mcp-elicitation requests and the agent scope's
  kill are covered by rows 30 and 8's own tests.
- The runbook's Overlay table describes every row on v0.1.6, the Cílový
  stack names each row's new commit and the files rows 13, 15, 16 and 18
  now change, and the swap step adds mobile-eas-preview-fork.yml to the
  workflows to disable after the swap. The runbook and the skill say to
  address a fix written over the finished stack to the row that added
  the place it changes.

On v0.1.7:

- CI and the contract test pin v0.1.7 and build 0.1.7-lazurio.0; the
  issue form's version example is 0.1.7-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
  v0.1.7 adds no workflow, so the swap step's list is unchanged.
- The allowlist gains toolkits/preview/handlers.ts and its test: since
  v0.1.7 preview_open takes a dev-server target (pingdotgg#28027),
  and upstream's handler answered an open with a target with the
  navigate result alone; row 10 keeps the open answer underneath, so the
  Environment browser's view stays. The fixed test gate is unchanged.
- The contract test follows the seams that moved: the settings writer
  takes the client's patch for the managed policy
  (updateAndPersistSettings, pingdotgg#27197), Hermes's runtime
  notes come from the active session setup, the MCP caller's webOrigin
  is now hostedAppUrl, the steer guard's waitsOnPendingRequest also
  holds a delegated task's question (pingdotgg#29909), and the
  ACP adapter filters T3's options through a flatMap.
- For row 30 the allowlist gains apps/web's components/ChatView.logic.ts
  and its test and components/chat/composerCommandKey.ts,
  client-runtime's state/composerDispatch.ts and its test, and
  contracts' orchestrationV2.ts: eight files with the two above. The
  contract test pins that the web keeps auto input auto while the run is
  set up; that /compact and /logout wait for no turn; that a running
  update takes the thread lock on its provider turn's first report or
  while a follow-up waits, then checks again under the lock; and that
  each follow-up gets one promotion, so a held one, one already promoted
  and a refused one stay queued without holding back the next.
- Stage 3's checkout command names the release version check's script
  and test (#165), which the v0.1.6 runbook left out.
- The runbook's Overlay table describes every row on v0.1.7, and the
  Cílový stack names each row's new commit. Main's Cílový stack still
  named older hashes from row 10 on, so the runbook and the skill now say
  to take each row's commit from main's log by subject. The runbook also
  records the Effect 4.1.2 test recipe (NodeCrypto beside NodeServices,
  ManagedPolicy.layerTest()) and that the overlay's settings writes go
  through updateSettingsWith, so the managed policy vets them.
- The runbook records what the independent check of this rebuild found:
  Codex 0.166.0, T3's managed runtime since v0.1.7, still has
  default_mode_request_user_input off by default (row 22); mcp-client
  sessions get hosted thread links on the external origin (row 20);
  upstream's star prompt now stars through the Environment's account
  (row 16); the policy lock reads the macOS and Windows sources too
  (row 18); two upstream policy paths in the update flow do not follow
  row 4's target and are offered upstream; row 30's refused promotion,
  /goal and cold-start steer; and row 33's steer page block. The overlay
  CLI tests build auth on the test managed policy.

On v0.1.8:

- CI and the contract test pin v0.1.8 and build 0.1.8-lazurio.0; the
  issue form's version example is 0.1.8-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy, whose contact is now
  security@t3.codes.
- The allowlist is unchanged. v0.1.8 adds no workflow, so the swap
  step's list is unchanged. Upstream's release-desktop.yml can now defer
  the macOS CLI's notarization with --notary-submission-file;
  lazurio-cli-archives.yml signs ad hoc, passes no such file and is
  unchanged.
- The contract test follows the seams that moved: the sidebar control
  takes showSidebar; the composer controls bar's hooks end with the
  model pick (pingdotgg#31739) and Buddy's controls return after
  them; an offered prompt suggestion comes before Buddy's placeholder
  (pingdotgg#28047); and a fresh session after /clear
  (pingdotgg#30325) never steers, in the web's dispatch mode and
  in the server's steer and promotion guards. Two new pins keep the
  Buddy surface's hides of upstream's new entries: "Use in another app"
  (decision A8) and /clear's fresh session (decision A7).
- The runbook's Overlay table describes every row on v0.1.8, the Cílový
  stack names each row's new commit and files (viewAddressCases.ts in
  rows 9 and 10), and row 30's text no longer compares
  waitsOnPendingRequest with snooze, which since v0.1.8 ignores a pending
  user_input. The runbook records this rebuild's conflicts and that a
  test the rebuild adds belongs in the row's own test file or under
  apps/*/src/lazurio/, since an upstream test file off the allowlist
  fails fork CI.

On v0.1.9:

- CI and the contract test pin v0.1.9 and build 0.1.9-lazurio.0; the
  issue form's version example is 0.1.9-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. Upstream left
  SECURITY.md unchanged, so its upstream section still equals the tag's
  policy.
- The allowlist is unchanged. The contract test's seams are unchanged
  apart from one new pin, and the tag and SHA pins move. The stack replays the approved v0.1.8 candidate
  (#187) on v0.1.9, and rows 4, 9, 15, 28 and 30 name
  their adaptations in their own messages.
- v0.1.9 adds mobile-dev-client.yml (push to main, pull_request on its
  own file and scripts/mobile-native-client.ts, workflow_dispatch); both its jobs run only in
  pingdotgg/t3code, and the swap step adds it to the workflows to
  disable after the swap. The changed ci.yml and four mobile workflows
  stay disabled.
- The runbook's Overlay table describes every row on v0.1.9, the
  Cílový stack names each row's new commit, and the runbook records
  this rebuild's conflicts and decisions. Upstream's new screen reader
  announcements (pingdotgg#33900) are capped at Buddy's messages on Buddy's
  surface, so a screen reader never hears T3's steps there (row 28);
  the contract test pins that cap in MessagesTimeline.tsx.

On v0.1.10:

- CI and the contract test pin v0.1.10 and build 0.1.10-lazurio.0; the
  issue form's version example is 0.1.10-lazurio.1. Upstream moved to
  Node 26.13.1 (pnpm 12.14.0 is unchanged), so CI, the release and the
  image pin Node 26.13.1 and node:26.13.1-bookworm by its index digest.
  Upstream left SECURITY.md unchanged, so its upstream section still
  equals the tag's policy; this row adds the fork's section to it.
- The allowlist drops branding.ts, ChatView.logic.ts and its test,
  composerCommandKey.ts and composerDispatch.ts and its test, which the
  overlay no longer changes: upstream now picks the stage label in
  branding.logic.ts, and it steers a follow-up sent before the provider
  turn started (pingdotgg#34581). Row 30 now turns an auto send
  made then into that deferred steer in Orchestrator.ts and marks it
  automatic on the queued run, so orchestrationV2.ts stays
  (#170). It adds sidebar/updateEverythingRun.tsx and its
  test, where row 4's Retry compares a Lazurio release's whole version,
  and three new upstream tests: SidebarUpdatePill.browser.test.tsx, whose rows carry
  row 4's per-row target; main.test.ts, whose stand-in window carries
  the address the prompt link capture reads (row 6); and binCli.test.ts,
  which reads row 21's `t3 thread list --json` with its total. The guard
  passes both ways on the candidate.
- The contract test follows the seams upstream moved: the launcher path
  now comes from cloud/pinnedRuntime.ts, the build stamps the page title
  from the stage label (pingdotgg#18442, and no release workflow
  sets VITE_HOSTED_APP_CHANNEL), ACP runtime instructions are one flag
  (sendRuntimeInstructions), the ACP adapter also resets unset options
  (pingdotgg#35199, held back on Buddy's instance too), provider
  hydration reads the database config (pingdotgg#34877), a
  natively resumed thread sends its unsent message
  (pingdotgg#36526), a failed send gives back the snapshot's
  draftText (pingdotgg#33124), a linked Environment's sender names
  it (pingdotgg#34721), an expandable work row's chevron sits
  between the acting-sender mark and the time (pingdotgg#35549),
  and the collapsed composer previews the prompt (pingdotgg#22148).
  Row 30's checks now pin that the one promote-to-steer is upstream's
  deferred steer, behind the pending-request guard that clears its
  steerWhenReadyRunId and steerWhenReadyIntent; the conditions under
  which an auto send in the gap becomes that steer, through
  resolveMessageDispatchIntent and the adapter's steering or
  interrupt-and-restart; and the delivery check that lets such a steer in
  only where the policy steers it then, by the session's capabilities.
- v0.1.10 adds issue-vouch.yml (issues, push to main on VOUCHED.td) and
  pr-limits.yml (pull_request_target and a daily schedule at 05:23 UTC;
  it labels, comments on and closes pull requests, dry-run without
  PR_LIMITS_ENFORCE). Both run on ubuntu-24.04 in the fork too, so the
  swap step disables them right after the swap. The swap push itself
  starts issue-vouch.yml, since it adds the workflow and VOUCHED.td, so
  the step first cancels that run and then removes any vouch label it
  gave an open issue.
- The Overlay table gains rows 35 to 37 for #214 and #216, and the
  Cílový stack names their commits on main and their files. Rows 4, 15,
  21 and 30 record the fixes from the candidate's independent check
  (#222); the rest of the table is brought up to v0.1.10
  after the release (stage 9). The runbook's "Z přestavby na v0.1.10"
  records the conflicts, the hand adaptations and those fixes, numbering
  rows as the table does, and names the replayed main (faae02a, stable
  0.1.9-lazurio.2: 0.1.9-lazurio.1 at 388b772 with #214 and #216).
- Main's #214, #216 and #220 additions to CI, the contract test and the
  runbook are carried unchanged; #216's narrow-rail pin follows row 36's
  `hidden` adaptation. A new contract pin holds row 35's hand-placed
  coordinator change: ThreadNotificationCoordinator.tsx reads hidden
  threads three times, always as listHiddenThreadKeysAtom, so Buddy's
  project's threads never sound, toast or notify.
- The review of the candidate at 50a5004 (#222) adds to
  the runbook: the contract inventory names orchestrationV2.ts with
  steerWhenReadyIntent only; rows 24 and 30 record the recorded
  followWakes and the auto steer that a question puts first in the
  queue; the F50 gate names holders.vectors.test.ts and the vendored
  Platform v0.1.22 vectors; the check that ~/.local/bin/t3 points to the
  new version reads both forms of the launcher, a symlink and since
  v0.1.10 the script posixLauncherScript writes; and the update channel
  and its procedure describe the launcher protocol's move from 3 to 4,
  which an Update from 0.1.9 passes while the 0.1.9 launcher stays until
  a local update or service install restarts the service. The contract
  test pins the copied release and the vectors' runner. After the next
  review row 24 records the wait before the send, so a repeat racing the
  first send cannot record its own; the runbook says so and drops the
  crash between send and record from the known limits.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
immakermatty added a commit that referenced this pull request Nov 18, 2026
The distribution's files on the new base, upstream T3 Code v0.1.10
(7d32075), last in the stack: CI,
the CLI archive, release and upstream watch workflows, the image, the
issue form, README, SECURITY.md, the runbook, the overlay spec, the
contract test, the release version check and the rebuild's skill. They
are main's files, made current for v0.1.10 (#213). Main's
base is v0.1.9 (#185); the notes for v0.1.4 to v0.1.9
below are kept from the earlier rebuilds.

On v0.1.4:

- The allowlist gains five files: chat/ThreadServersPanel.tsx, where a
  click on a thread's server opens it in the Environment browser (row 9);
  sidebar/UpdateEverythingDialog.tsx and updateEverything.logic.test.ts,
  for the per-server target and the continuation gate of v0.1.4's update
  dialog (row 4); upstream's installer test install.test.ts, whose fixture
  needs upstream's repository named (row 4); and cli/environment.ts, whose
  settings take Buddy's linked-Environments guard (row 25).
  ServerEnvironment.test.ts keeps the update-check guard (row 4).
- The contract test's pins follow the seams that moved: upstream deleted
  LegacySidebar.tsx (pingdotgg#21039), so the shell slot's column
  head is pinned in the thread sidebar only; the sidebar reads
  useDelegatedUnderParent before the managed check; the empty panel and
  Nová karta carry the workspace focus default; the MCP session issue
  calls mcpClientScopes directly; an agent command's scope drops the
  session's web origin so its thread links stay t3-thread:// links; the
  Buddy composer hook takes only the environment, since v0.1.4's resting
  composer has no strip of its own; the timeline has no paint-only gate
  (pingdotgg#25787); the steer guard returns through
  stopRunForQueuedCommand and also holds a delegated task's completion
  wake; the Servers panel's click opens the Environment browser; and
  Buddy's server settings layer turns linked Environments off.
- Rows 30, 32 and 33, which main carried as commits after row 31, now
  sit in their rows; row 28's addenda are back in rows 7, 23 and 25.
  Upstream renamed the lint rule react-effect-budget to
  t3code/no-unreasoned-state-sync (pingdotgg#26161).
- The skill's inventory groups cover rows 23 to 33.
- Tests, fixtures and docs of rows 9, 10, 21, 23, 25, 26 and 27 name
  only fictional people and hosts (Alena, Bob, example-person,
  vm-0x.example.lazurio.io), since the repository is public.

On v0.1.5:

- CI and the contract test pin v0.1.5 and build 0.1.5-lazurio.0; the
  issue form's version example is 0.1.5-lazurio.1. Node 26.12.1 and pnpm
  12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy.
- The Linux CLI archive now ships lib/libatomic.so.1 and patchelf sets
  t3's RUNPATH to it (pingdotgg#26912, pingdotgg#26932), so
  lazurio-cli-archives.yml installs patchelf before the build, the way
  upstream's release-desktop.yml does; the contract test pins the order.
- useUpdateEverything.ts leaves the allowlist: row 4 now keeps a
  server's advertised release out of waitForNpm in
  updateEverything.logic.ts (pingdotgg#26917), and the contract
  test pins that seam there. The fixed test gate is unchanged, and every
  gated path exists at v0.1.5.
- The contract test's pairing pins follow the constants that knip made
  module-private (upstream's pre-commit hook runs knip:check since
  pingdotgg#26167).
- The runbook's Overlay table describes every row on v0.1.5, the Cílový
  stack names each row's new commit, the swap step names the workflows
  to disable after the swap from the v0.1.3 base (agent-context-budget.yml,
  mobile-fingerprint-label.yml; v0.1.5 adds none), and stage 3 and the
  skill say to replay with --no-verify and run knip over the finished
  stack.

On v0.1.6:

- CI and the contract test pin v0.1.6 and build 0.1.6-lazurio.0; the
  issue form's version example is 0.1.6-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
- The allowlist is unchanged. Its comments say why ServerEnvironment.ts
  and server.ts offer and build no triage on a Lazurio Environment
  (row 15, #147), why ws.ts runs no ChatGPT handoff there
  and the web starts none through a Lazurio primary (row 18,
  #145), that useComposerSend.ts counts a prompt toward
  upstream's star request (pingdotgg#27832) only outside a Lazurio
  Environment (row 16), and that no update waits on npm since
  pingdotgg#27847 (row 4).
- The contract test pins those seams: the triage guard and its one
  construction, the star prompt's check and its one call, the handoff
  route, reconnectProfile and the web's routing, and on Buddy's surface
  the inline mask over useThreadLifecycle's attentionNow and workNow,
  every line of it (React Compiler, #135), the items'
  counts in useThreadLifecycle.tsx and its one caller, the promise
  ChatView hands Nová karta for a side chat (row 13), and that Buddy's
  surface offers no side chat (row 25). It also follows
  the seams upstream moved: no waitForNpm left in the update dialog's
  logic, the palette's addProjectAction, the sidebar's pickable project
  groups (pingdotgg#26154), and an embedded side chat
  (pingdotgg#26901) without thread tabs, terminal drawers or the
  right panel. Claude's mcp-elicitation requests and the agent scope's
  kill are covered by rows 30 and 8's own tests.
- The runbook's Overlay table describes every row on v0.1.6, the Cílový
  stack names each row's new commit and the files rows 13, 15, 16 and 18
  now change, and the swap step adds mobile-eas-preview-fork.yml to the
  workflows to disable after the swap. The runbook and the skill say to
  address a fix written over the finished stack to the row that added
  the place it changes.

On v0.1.7:

- CI and the contract test pin v0.1.7 and build 0.1.7-lazurio.0; the
  issue form's version example is 0.1.7-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
  v0.1.7 adds no workflow, so the swap step's list is unchanged.
- The allowlist gains toolkits/preview/handlers.ts and its test: since
  v0.1.7 preview_open takes a dev-server target (pingdotgg#28027),
  and upstream's handler answered an open with a target with the
  navigate result alone; row 10 keeps the open answer underneath, so the
  Environment browser's view stays. The fixed test gate is unchanged.
- The contract test follows the seams that moved: the settings writer
  takes the client's patch for the managed policy
  (updateAndPersistSettings, pingdotgg#27197), Hermes's runtime
  notes come from the active session setup, the MCP caller's webOrigin
  is now hostedAppUrl, the steer guard's waitsOnPendingRequest also
  holds a delegated task's question (pingdotgg#29909), and the
  ACP adapter filters T3's options through a flatMap.
- For row 30 the allowlist gains apps/web's components/ChatView.logic.ts
  and its test and components/chat/composerCommandKey.ts,
  client-runtime's state/composerDispatch.ts and its test, and
  contracts' orchestrationV2.ts: eight files with the two above. The
  contract test pins that the web keeps auto input auto while the run is
  set up; that /compact and /logout wait for no turn; that a running
  update takes the thread lock on its provider turn's first report or
  while a follow-up waits, then checks again under the lock; and that
  each follow-up gets one promotion, so a held one, one already promoted
  and a refused one stay queued without holding back the next.
- Stage 3's checkout command names the release version check's script
  and test (#165), which the v0.1.6 runbook left out.
- The runbook's Overlay table describes every row on v0.1.7, and the
  Cílový stack names each row's new commit. Main's Cílový stack still
  named older hashes from row 10 on, so the runbook and the skill now say
  to take each row's commit from main's log by subject. The runbook also
  records the Effect 4.1.2 test recipe (NodeCrypto beside NodeServices,
  ManagedPolicy.layerTest()) and that the overlay's settings writes go
  through updateSettingsWith, so the managed policy vets them.
- The runbook records what the independent check of this rebuild found:
  Codex 0.166.0, T3's managed runtime since v0.1.7, still has
  default_mode_request_user_input off by default (row 22); mcp-client
  sessions get hosted thread links on the external origin (row 20);
  upstream's star prompt now stars through the Environment's account
  (row 16); the policy lock reads the macOS and Windows sources too
  (row 18); two upstream policy paths in the update flow do not follow
  row 4's target and are offered upstream; row 30's refused promotion,
  /goal and cold-start steer; and row 33's steer page block. The overlay
  CLI tests build auth on the test managed policy.

On v0.1.8:

- CI and the contract test pin v0.1.8 and build 0.1.8-lazurio.0; the
  issue form's version example is 0.1.8-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy, whose contact is now
  security@t3.codes.
- The allowlist is unchanged. v0.1.8 adds no workflow, so the swap
  step's list is unchanged. Upstream's release-desktop.yml can now defer
  the macOS CLI's notarization with --notary-submission-file;
  lazurio-cli-archives.yml signs ad hoc, passes no such file and is
  unchanged.
- The contract test follows the seams that moved: the sidebar control
  takes showSidebar; the composer controls bar's hooks end with the
  model pick (pingdotgg#31739) and Buddy's controls return after
  them; an offered prompt suggestion comes before Buddy's placeholder
  (pingdotgg#28047); and a fresh session after /clear
  (pingdotgg#30325) never steers, in the web's dispatch mode and
  in the server's steer and promotion guards. Two new pins keep the
  Buddy surface's hides of upstream's new entries: "Use in another app"
  (decision A8) and /clear's fresh session (decision A7).
- The runbook's Overlay table describes every row on v0.1.8, the Cílový
  stack names each row's new commit and files (viewAddressCases.ts in
  rows 9 and 10), and row 30's text no longer compares
  waitsOnPendingRequest with snooze, which since v0.1.8 ignores a pending
  user_input. The runbook records this rebuild's conflicts and that a
  test the rebuild adds belongs in the row's own test file or under
  apps/*/src/lazurio/, since an upstream test file off the allowlist
  fails fork CI.

On v0.1.9:

- CI and the contract test pin v0.1.9 and build 0.1.9-lazurio.0; the
  issue form's version example is 0.1.9-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. Upstream left
  SECURITY.md unchanged, so its upstream section still equals the tag's
  policy.
- The allowlist is unchanged. The contract test's seams are unchanged
  apart from one new pin, and the tag and SHA pins move. The stack replays the approved v0.1.8 candidate
  (#187) on v0.1.9, and rows 4, 9, 15, 28 and 30 name
  their adaptations in their own messages.
- v0.1.9 adds mobile-dev-client.yml (push to main, pull_request on its
  own file and scripts/mobile-native-client.ts, workflow_dispatch); both its jobs run only in
  pingdotgg/t3code, and the swap step adds it to the workflows to
  disable after the swap. The changed ci.yml and four mobile workflows
  stay disabled.
- The runbook's Overlay table describes every row on v0.1.9, the
  Cílový stack names each row's new commit, and the runbook records
  this rebuild's conflicts and decisions. Upstream's new screen reader
  announcements (pingdotgg#33900) are capped at Buddy's messages on Buddy's
  surface, so a screen reader never hears T3's steps there (row 28);
  the contract test pins that cap in MessagesTimeline.tsx.

On v0.1.10:

- CI and the contract test pin v0.1.10 and build 0.1.10-lazurio.0; the
  issue form's version example is 0.1.10-lazurio.1. Upstream moved to
  Node 26.13.1 (pnpm 12.14.0 is unchanged), so CI, the release and the
  image pin Node 26.13.1 and node:26.13.1-bookworm by its index digest.
  Upstream left SECURITY.md unchanged, so its upstream section still
  equals the tag's policy; this row adds the fork's section to it.
- The allowlist drops branding.ts, ChatView.logic.ts and its test,
  composerCommandKey.ts and composerDispatch.ts and its test, which the
  overlay no longer changes: upstream now picks the stage label in
  branding.logic.ts, and it steers a follow-up sent before the provider
  turn started (pingdotgg#34581). Row 30 now turns an auto send
  made then into that deferred steer in Orchestrator.ts and marks it
  automatic on the queued run, so orchestrationV2.ts stays
  (#170). It adds sidebar/updateEverythingRun.tsx and its
  test, where row 4's Retry compares a Lazurio release's whole version,
  and three new upstream tests: SidebarUpdatePill.browser.test.tsx, whose rows carry
  row 4's per-row target; main.test.ts, whose stand-in window carries
  the address the prompt link capture reads (row 6); and binCli.test.ts,
  which reads row 21's `t3 thread list --json` with its total. The guard
  passes both ways on the candidate.
- The contract test follows the seams upstream moved: the launcher path
  now comes from cloud/pinnedRuntime.ts, the build stamps the page title
  from the stage label (pingdotgg#18442, and no release workflow
  sets VITE_HOSTED_APP_CHANNEL), ACP runtime instructions are one flag
  (sendRuntimeInstructions), the ACP adapter also resets unset options
  (pingdotgg#35199, held back on Buddy's instance too), provider
  hydration reads the database config (pingdotgg#34877), a
  natively resumed thread sends its unsent message
  (pingdotgg#36526), a failed send gives back the snapshot's
  draftText (pingdotgg#33124), a linked Environment's sender names
  it (pingdotgg#34721), an expandable work row's chevron sits
  between the acting-sender mark and the time (pingdotgg#35549),
  and the collapsed composer previews the prompt (pingdotgg#22148).
  Row 30's checks now pin that the one promote-to-steer is upstream's
  deferred steer, behind the pending-request guard that clears its
  steerWhenReadyRunId and steerWhenReadyIntent; the conditions under
  which an auto send in the gap becomes that steer, through
  resolveMessageDispatchIntent and the adapter's steering or
  interrupt-and-restart; and the delivery check that lets such a steer in
  only where the policy steers it then, by the session's capabilities.
- v0.1.10 adds issue-vouch.yml (issues, push to main on VOUCHED.td) and
  pr-limits.yml (pull_request_target and a daily schedule at 05:23 UTC;
  it labels, comments on and closes pull requests, dry-run without
  PR_LIMITS_ENFORCE). Both run on ubuntu-24.04 in the fork too, so the
  swap step disables them right after the swap. The swap push itself
  starts issue-vouch.yml, since it adds the workflow and VOUCHED.td, so
  the step first cancels that run and then removes any vouch label it
  gave an open issue.
- The Overlay table gains rows 35 to 37 for #214 and #216, and the
  Cílový stack names their commits on main and their files. Rows 4, 15,
  21 and 30 record the fixes from the candidate's independent check
  (#222); the rest of the table is brought up to v0.1.10
  after the release (stage 9). The runbook's "Z přestavby na v0.1.10"
  records the conflicts, the hand adaptations and those fixes, numbering
  rows as the table does, and names the replayed main (faae02a, stable
  0.1.9-lazurio.2: 0.1.9-lazurio.1 at 388b772 with #214 and #216).
- Main's #214, #216 and #220 additions to CI, the contract test and the
  runbook are carried unchanged; #216's narrow-rail pin follows row 36's
  `hidden` adaptation. A new contract pin holds row 35's hand-placed
  coordinator change: ThreadNotificationCoordinator.tsx reads hidden
  threads three times, always as listHiddenThreadKeysAtom, so Buddy's
  project's threads never sound, toast or notify.
- The review of the candidate at 50a5004 (#222) adds to
  the runbook: the contract inventory names orchestrationV2.ts with
  steerWhenReadyIntent only; rows 24 and 30 record the recorded
  followWakes and the auto steer that a question puts first in the
  queue; the F50 gate names holders.vectors.test.ts and the vendored
  Platform v0.1.22 vectors; the check that ~/.local/bin/t3 points to the
  new version reads both forms of the launcher, a symlink and since
  v0.1.10 the script posixLauncherScript writes; and the update channel
  and its procedure describe the launcher protocol's move from 3 to 4,
  which an Update from 0.1.9 passes while the 0.1.9 launcher stays until
  a local update or service install restarts the service. The contract
  test pins the copied release and the vectors' runner. After the next
  review row 24 records the wait before the send, so a repeat racing the
  first send cannot record its own; the runbook says so and drops the
  crash between send and record from the known limits. After the review
  after that, T3 records the wait only until it accepts the key's command
  and each send reads the last record after it sent, so a send that
  fails between record and dispatch leaves no wait a retry follows; the
  contract test pins the record before the send, the read after it and
  the receipt check.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
immakermatty added a commit that referenced this pull request Nov 18, 2026
The distribution's files on the new base, upstream T3 Code v0.1.10
(7d32075), last in the stack: CI,
the CLI archive, release and upstream watch workflows, the image, the
issue form, README, SECURITY.md, the runbook, the overlay spec, the
contract test, the release version check and the rebuild's skill. They
are main's files, made current for v0.1.10 (#213). Main's
base is v0.1.9 (#185); the notes for v0.1.4 to v0.1.9
below are kept from the earlier rebuilds.

On v0.1.4:

- The allowlist gains five files: chat/ThreadServersPanel.tsx, where a
  click on a thread's server opens it in the Environment browser (row 9);
  sidebar/UpdateEverythingDialog.tsx and updateEverything.logic.test.ts,
  for the per-server target and the continuation gate of v0.1.4's update
  dialog (row 4); upstream's installer test install.test.ts, whose fixture
  needs upstream's repository named (row 4); and cli/environment.ts, whose
  settings take Buddy's linked-Environments guard (row 25).
  ServerEnvironment.test.ts keeps the update-check guard (row 4).
- The contract test's pins follow the seams that moved: upstream deleted
  LegacySidebar.tsx (pingdotgg#21039), so the shell slot's column
  head is pinned in the thread sidebar only; the sidebar reads
  useDelegatedUnderParent before the managed check; the empty panel and
  Nová karta carry the workspace focus default; the MCP session issue
  calls mcpClientScopes directly; an agent command's scope drops the
  session's web origin so its thread links stay t3-thread:// links; the
  Buddy composer hook takes only the environment, since v0.1.4's resting
  composer has no strip of its own; the timeline has no paint-only gate
  (pingdotgg#25787); the steer guard returns through
  stopRunForQueuedCommand and also holds a delegated task's completion
  wake; the Servers panel's click opens the Environment browser; and
  Buddy's server settings layer turns linked Environments off.
- Rows 30, 32 and 33, which main carried as commits after row 31, now
  sit in their rows; row 28's addenda are back in rows 7, 23 and 25.
  Upstream renamed the lint rule react-effect-budget to
  t3code/no-unreasoned-state-sync (pingdotgg#26161).
- The skill's inventory groups cover rows 23 to 33.
- Tests, fixtures and docs of rows 9, 10, 21, 23, 25, 26 and 27 name
  only fictional people and hosts (Alena, Bob, example-person,
  vm-0x.example.lazurio.io), since the repository is public.

On v0.1.5:

- CI and the contract test pin v0.1.5 and build 0.1.5-lazurio.0; the
  issue form's version example is 0.1.5-lazurio.1. Node 26.12.1 and pnpm
  12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy.
- The Linux CLI archive now ships lib/libatomic.so.1 and patchelf sets
  t3's RUNPATH to it (pingdotgg#26912, pingdotgg#26932), so
  lazurio-cli-archives.yml installs patchelf before the build, the way
  upstream's release-desktop.yml does; the contract test pins the order.
- useUpdateEverything.ts leaves the allowlist: row 4 now keeps a
  server's advertised release out of waitForNpm in
  updateEverything.logic.ts (pingdotgg#26917), and the contract
  test pins that seam there. The fixed test gate is unchanged, and every
  gated path exists at v0.1.5.
- The contract test's pairing pins follow the constants that knip made
  module-private (upstream's pre-commit hook runs knip:check since
  pingdotgg#26167).
- The runbook's Overlay table describes every row on v0.1.5, the Cílový
  stack names each row's new commit, the swap step names the workflows
  to disable after the swap from the v0.1.3 base (agent-context-budget.yml,
  mobile-fingerprint-label.yml; v0.1.5 adds none), and stage 3 and the
  skill say to replay with --no-verify and run knip over the finished
  stack.

On v0.1.6:

- CI and the contract test pin v0.1.6 and build 0.1.6-lazurio.0; the
  issue form's version example is 0.1.6-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
- The allowlist is unchanged. Its comments say why ServerEnvironment.ts
  and server.ts offer and build no triage on a Lazurio Environment
  (row 15, #147), why ws.ts runs no ChatGPT handoff there
  and the web starts none through a Lazurio primary (row 18,
  #145), that useComposerSend.ts counts a prompt toward
  upstream's star request (pingdotgg#27832) only outside a Lazurio
  Environment (row 16), and that no update waits on npm since
  pingdotgg#27847 (row 4).
- The contract test pins those seams: the triage guard and its one
  construction, the star prompt's check and its one call, the handoff
  route, reconnectProfile and the web's routing, and on Buddy's surface
  the inline mask over useThreadLifecycle's attentionNow and workNow,
  every line of it (React Compiler, #135), the items'
  counts in useThreadLifecycle.tsx and its one caller, the promise
  ChatView hands Nová karta for a side chat (row 13), and that Buddy's
  surface offers no side chat (row 25). It also follows
  the seams upstream moved: no waitForNpm left in the update dialog's
  logic, the palette's addProjectAction, the sidebar's pickable project
  groups (pingdotgg#26154), and an embedded side chat
  (pingdotgg#26901) without thread tabs, terminal drawers or the
  right panel. Claude's mcp-elicitation requests and the agent scope's
  kill are covered by rows 30 and 8's own tests.
- The runbook's Overlay table describes every row on v0.1.6, the Cílový
  stack names each row's new commit and the files rows 13, 15, 16 and 18
  now change, and the swap step adds mobile-eas-preview-fork.yml to the
  workflows to disable after the swap. The runbook and the skill say to
  address a fix written over the finished stack to the row that added
  the place it changes.

On v0.1.7:

- CI and the contract test pin v0.1.7 and build 0.1.7-lazurio.0; the
  issue form's version example is 0.1.7-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
  v0.1.7 adds no workflow, so the swap step's list is unchanged.
- The allowlist gains toolkits/preview/handlers.ts and its test: since
  v0.1.7 preview_open takes a dev-server target (pingdotgg#28027),
  and upstream's handler answered an open with a target with the
  navigate result alone; row 10 keeps the open answer underneath, so the
  Environment browser's view stays. The fixed test gate is unchanged.
- The contract test follows the seams that moved: the settings writer
  takes the client's patch for the managed policy
  (updateAndPersistSettings, pingdotgg#27197), Hermes's runtime
  notes come from the active session setup, the MCP caller's webOrigin
  is now hostedAppUrl, the steer guard's waitsOnPendingRequest also
  holds a delegated task's question (pingdotgg#29909), and the
  ACP adapter filters T3's options through a flatMap.
- For row 30 the allowlist gains apps/web's components/ChatView.logic.ts
  and its test and components/chat/composerCommandKey.ts,
  client-runtime's state/composerDispatch.ts and its test, and
  contracts' orchestrationV2.ts: eight files with the two above. The
  contract test pins that the web keeps auto input auto while the run is
  set up; that /compact and /logout wait for no turn; that a running
  update takes the thread lock on its provider turn's first report or
  while a follow-up waits, then checks again under the lock; and that
  each follow-up gets one promotion, so a held one, one already promoted
  and a refused one stay queued without holding back the next.
- Stage 3's checkout command names the release version check's script
  and test (#165), which the v0.1.6 runbook left out.
- The runbook's Overlay table describes every row on v0.1.7, and the
  Cílový stack names each row's new commit. Main's Cílový stack still
  named older hashes from row 10 on, so the runbook and the skill now say
  to take each row's commit from main's log by subject. The runbook also
  records the Effect 4.1.2 test recipe (NodeCrypto beside NodeServices,
  ManagedPolicy.layerTest()) and that the overlay's settings writes go
  through updateSettingsWith, so the managed policy vets them.
- The runbook records what the independent check of this rebuild found:
  Codex 0.166.0, T3's managed runtime since v0.1.7, still has
  default_mode_request_user_input off by default (row 22); mcp-client
  sessions get hosted thread links on the external origin (row 20);
  upstream's star prompt now stars through the Environment's account
  (row 16); the policy lock reads the macOS and Windows sources too
  (row 18); two upstream policy paths in the update flow do not follow
  row 4's target and are offered upstream; row 30's refused promotion,
  /goal and cold-start steer; and row 33's steer page block. The overlay
  CLI tests build auth on the test managed policy.

On v0.1.8:

- CI and the contract test pin v0.1.8 and build 0.1.8-lazurio.0; the
  issue form's version example is 0.1.8-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy, whose contact is now
  security@t3.codes.
- The allowlist is unchanged. v0.1.8 adds no workflow, so the swap
  step's list is unchanged. Upstream's release-desktop.yml can now defer
  the macOS CLI's notarization with --notary-submission-file;
  lazurio-cli-archives.yml signs ad hoc, passes no such file and is
  unchanged.
- The contract test follows the seams that moved: the sidebar control
  takes showSidebar; the composer controls bar's hooks end with the
  model pick (pingdotgg#31739) and Buddy's controls return after
  them; an offered prompt suggestion comes before Buddy's placeholder
  (pingdotgg#28047); and a fresh session after /clear
  (pingdotgg#30325) never steers, in the web's dispatch mode and
  in the server's steer and promotion guards. Two new pins keep the
  Buddy surface's hides of upstream's new entries: "Use in another app"
  (decision A8) and /clear's fresh session (decision A7).
- The runbook's Overlay table describes every row on v0.1.8, the Cílový
  stack names each row's new commit and files (viewAddressCases.ts in
  rows 9 and 10), and row 30's text no longer compares
  waitsOnPendingRequest with snooze, which since v0.1.8 ignores a pending
  user_input. The runbook records this rebuild's conflicts and that a
  test the rebuild adds belongs in the row's own test file or under
  apps/*/src/lazurio/, since an upstream test file off the allowlist
  fails fork CI.

On v0.1.9:

- CI and the contract test pin v0.1.9 and build 0.1.9-lazurio.0; the
  issue form's version example is 0.1.9-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. Upstream left
  SECURITY.md unchanged, so its upstream section still equals the tag's
  policy.
- The allowlist is unchanged. The contract test's seams are unchanged
  apart from one new pin, and the tag and SHA pins move. The stack replays the approved v0.1.8 candidate
  (#187) on v0.1.9, and rows 4, 9, 15, 28 and 30 name
  their adaptations in their own messages.
- v0.1.9 adds mobile-dev-client.yml (push to main, pull_request on its
  own file and scripts/mobile-native-client.ts, workflow_dispatch); both its jobs run only in
  pingdotgg/t3code, and the swap step adds it to the workflows to
  disable after the swap. The changed ci.yml and four mobile workflows
  stay disabled.
- The runbook's Overlay table describes every row on v0.1.9, the
  Cílový stack names each row's new commit, and the runbook records
  this rebuild's conflicts and decisions. Upstream's new screen reader
  announcements (pingdotgg#33900) are capped at Buddy's messages on Buddy's
  surface, so a screen reader never hears T3's steps there (row 28);
  the contract test pins that cap in MessagesTimeline.tsx.

On v0.1.10:

- CI and the contract test pin v0.1.10 and build 0.1.10-lazurio.0; the
  issue form's version example is 0.1.10-lazurio.1. Upstream moved to
  Node 26.13.1 (pnpm 12.14.0 is unchanged), so CI, the release and the
  image pin Node 26.13.1 and node:26.13.1-bookworm by its index digest.
  Upstream left SECURITY.md unchanged, so its upstream section still
  equals the tag's policy; this row adds the fork's section to it.
- The allowlist drops branding.ts, ChatView.logic.ts and its test,
  composerCommandKey.ts and composerDispatch.ts and its test, which the
  overlay no longer changes: upstream now picks the stage label in
  branding.logic.ts, and it steers a follow-up sent before the provider
  turn started (pingdotgg#34581). Row 30 now turns an auto send
  made then into that deferred steer in Orchestrator.ts and marks it
  automatic on the queued run, so orchestrationV2.ts stays
  (#170). It adds sidebar/updateEverythingRun.tsx and its
  test, where row 4's Retry compares a Lazurio release's whole version,
  and three new upstream tests: SidebarUpdatePill.browser.test.tsx, whose rows carry
  row 4's per-row target; main.test.ts, whose stand-in window carries
  the address the prompt link capture reads (row 6); and binCli.test.ts,
  which reads row 21's `t3 thread list --json` with its total. The guard
  passes both ways on the candidate.
- The contract test follows the seams upstream moved: the launcher path
  now comes from cloud/pinnedRuntime.ts, the build stamps the page title
  from the stage label (pingdotgg#18442, and no release workflow
  sets VITE_HOSTED_APP_CHANNEL), ACP runtime instructions are one flag
  (sendRuntimeInstructions), the ACP adapter also resets unset options
  (pingdotgg#35199, held back on Buddy's instance too), provider
  hydration reads the database config (pingdotgg#34877), a
  natively resumed thread sends its unsent message
  (pingdotgg#36526), a failed send gives back the snapshot's
  draftText (pingdotgg#33124), a linked Environment's sender names
  it (pingdotgg#34721), an expandable work row's chevron sits
  between the acting-sender mark and the time (pingdotgg#35549),
  and the collapsed composer previews the prompt (pingdotgg#22148).
  Row 30's checks now pin that the one promote-to-steer is upstream's
  deferred steer, behind the pending-request guard that clears its
  steerWhenReadyRunId and steerWhenReadyIntent; the conditions under
  which an auto send in the gap becomes that steer, through
  resolveMessageDispatchIntent and the adapter's steering or
  interrupt-and-restart; and the delivery check that lets such a steer in
  only where the policy steers it then, by the session's capabilities.
- v0.1.10 adds issue-vouch.yml (issues, push to main on VOUCHED.td) and
  pr-limits.yml (pull_request_target and a daily schedule at 05:23 UTC;
  it labels, comments on and closes pull requests, dry-run without
  PR_LIMITS_ENFORCE). Both run on ubuntu-24.04 in the fork too, so the
  swap step disables them right after the swap. The swap push itself
  starts issue-vouch.yml, since it adds the workflow and VOUCHED.td, so
  the step first cancels that run and then removes any vouch label it
  gave an open issue.
- The Overlay table gains rows 35 to 37 for #214 and #216, and the
  Cílový stack names their commits on main and their files. Rows 4, 15,
  21 and 30 record the fixes from the candidate's independent check
  (#222); the rest of the table is brought up to v0.1.10
  after the release (stage 9). The runbook's "Z přestavby na v0.1.10"
  records the conflicts, the hand adaptations and those fixes, numbering
  rows as the table does, and names the replayed main (faae02a, stable
  0.1.9-lazurio.2: 0.1.9-lazurio.1 at 388b772 with #214 and #216).
- Main's #214, #216 and #220 additions to CI, the contract test and the
  runbook are carried unchanged; #216's narrow-rail pin follows row 36's
  `hidden` adaptation. A new contract pin holds row 35's hand-placed
  coordinator change: ThreadNotificationCoordinator.tsx reads hidden
  threads three times, always as listHiddenThreadKeysAtom, so Buddy's
  project's threads never sound, toast or notify.
- The review of the candidate at 50a5004 (#222) adds to
  the runbook: the contract inventory names orchestrationV2.ts with
  steerWhenReadyIntent only; rows 24 and 30 record the recorded
  followWakes and the auto steer that a question puts first in the
  queue; the F50 gate names holders.vectors.test.ts and the vendored
  Platform v0.1.22 vectors; the check that ~/.local/bin/t3 points to the
  new version reads both forms of the launcher, a symlink and since
  v0.1.10 the script posixLauncherScript writes; and the update channel
  and its procedure describe the launcher protocol's move from 3 to 4,
  which an Update from 0.1.9 passes while the 0.1.9 launcher stays until
  a local update or service install restarts the service. The contract
  test pins the copied release and the vectors' runner. After the next
  review row 24 records the wait before the send, so a repeat racing the
  first send cannot record its own; the runbook says so and drops the
  crash between send and record from the known limits. After the review
  after that, T3 records the wait only until it accepts the key's command
  and each send reads the last record after it sent, so a send that
  fails between record and dispatch leaves no wait a retry follows; the
  contract test pins the record before the send, the read after it and
  the receipt check. After the review on c5cf16b, each keyed send claims
  its key before it sends and only the claim's holder sends, so the wait
  T3 keeps is the accepted send's; the runbook describes the claim, the
  send_in_progress refusal, CLAIM_TTL_MS and the limits, and the
  contract test pins the claim, the refusal, the release, the expiry and
  the receipt gate.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
immakermatty added a commit that referenced this pull request Nov 18, 2026
The distribution's files on the new base, upstream T3 Code v0.1.10
(7d32075), last in the stack: CI,
the CLI archive, release and upstream watch workflows, the image, the
issue form, README, SECURITY.md, the runbook, the overlay spec, the
contract test, the release version check and the rebuild's skill. They
are main's files, made current for v0.1.10 (#213). Main's
base is v0.1.9 (#185); the notes for v0.1.4 to v0.1.9
below are kept from the earlier rebuilds.

On v0.1.4:

- The allowlist gains five files: chat/ThreadServersPanel.tsx, where a
  click on a thread's server opens it in the Environment browser (row 9);
  sidebar/UpdateEverythingDialog.tsx and updateEverything.logic.test.ts,
  for the per-server target and the continuation gate of v0.1.4's update
  dialog (row 4); upstream's installer test install.test.ts, whose fixture
  needs upstream's repository named (row 4); and cli/environment.ts, whose
  settings take Buddy's linked-Environments guard (row 25).
  ServerEnvironment.test.ts keeps the update-check guard (row 4).
- The contract test's pins follow the seams that moved: upstream deleted
  LegacySidebar.tsx (pingdotgg#21039), so the shell slot's column
  head is pinned in the thread sidebar only; the sidebar reads
  useDelegatedUnderParent before the managed check; the empty panel and
  Nová karta carry the workspace focus default; the MCP session issue
  calls mcpClientScopes directly; an agent command's scope drops the
  session's web origin so its thread links stay t3-thread:// links; the
  Buddy composer hook takes only the environment, since v0.1.4's resting
  composer has no strip of its own; the timeline has no paint-only gate
  (pingdotgg#25787); the steer guard returns through
  stopRunForQueuedCommand and also holds a delegated task's completion
  wake; the Servers panel's click opens the Environment browser; and
  Buddy's server settings layer turns linked Environments off.
- Rows 30, 32 and 33, which main carried as commits after row 31, now
  sit in their rows; row 28's addenda are back in rows 7, 23 and 25.
  Upstream renamed the lint rule react-effect-budget to
  t3code/no-unreasoned-state-sync (pingdotgg#26161).
- The skill's inventory groups cover rows 23 to 33.
- Tests, fixtures and docs of rows 9, 10, 21, 23, 25, 26 and 27 name
  only fictional people and hosts (Alena, Bob, example-person,
  vm-0x.example.lazurio.io), since the repository is public.

On v0.1.5:

- CI and the contract test pin v0.1.5 and build 0.1.5-lazurio.0; the
  issue form's version example is 0.1.5-lazurio.1. Node 26.12.1 and pnpm
  12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy.
- The Linux CLI archive now ships lib/libatomic.so.1 and patchelf sets
  t3's RUNPATH to it (pingdotgg#26912, pingdotgg#26932), so
  lazurio-cli-archives.yml installs patchelf before the build, the way
  upstream's release-desktop.yml does; the contract test pins the order.
- useUpdateEverything.ts leaves the allowlist: row 4 now keeps a
  server's advertised release out of waitForNpm in
  updateEverything.logic.ts (pingdotgg#26917), and the contract
  test pins that seam there. The fixed test gate is unchanged, and every
  gated path exists at v0.1.5.
- The contract test's pairing pins follow the constants that knip made
  module-private (upstream's pre-commit hook runs knip:check since
  pingdotgg#26167).
- The runbook's Overlay table describes every row on v0.1.5, the Cílový
  stack names each row's new commit, the swap step names the workflows
  to disable after the swap from the v0.1.3 base (agent-context-budget.yml,
  mobile-fingerprint-label.yml; v0.1.5 adds none), and stage 3 and the
  skill say to replay with --no-verify and run knip over the finished
  stack.

On v0.1.6:

- CI and the contract test pin v0.1.6 and build 0.1.6-lazurio.0; the
  issue form's version example is 0.1.6-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
- The allowlist is unchanged. Its comments say why ServerEnvironment.ts
  and server.ts offer and build no triage on a Lazurio Environment
  (row 15, #147), why ws.ts runs no ChatGPT handoff there
  and the web starts none through a Lazurio primary (row 18,
  #145), that useComposerSend.ts counts a prompt toward
  upstream's star request (pingdotgg#27832) only outside a Lazurio
  Environment (row 16), and that no update waits on npm since
  pingdotgg#27847 (row 4).
- The contract test pins those seams: the triage guard and its one
  construction, the star prompt's check and its one call, the handoff
  route, reconnectProfile and the web's routing, and on Buddy's surface
  the inline mask over useThreadLifecycle's attentionNow and workNow,
  every line of it (React Compiler, #135), the items'
  counts in useThreadLifecycle.tsx and its one caller, the promise
  ChatView hands Nová karta for a side chat (row 13), and that Buddy's
  surface offers no side chat (row 25). It also follows
  the seams upstream moved: no waitForNpm left in the update dialog's
  logic, the palette's addProjectAction, the sidebar's pickable project
  groups (pingdotgg#26154), and an embedded side chat
  (pingdotgg#26901) without thread tabs, terminal drawers or the
  right panel. Claude's mcp-elicitation requests and the agent scope's
  kill are covered by rows 30 and 8's own tests.
- The runbook's Overlay table describes every row on v0.1.6, the Cílový
  stack names each row's new commit and the files rows 13, 15, 16 and 18
  now change, and the swap step adds mobile-eas-preview-fork.yml to the
  workflows to disable after the swap. The runbook and the skill say to
  address a fix written over the finished stack to the row that added
  the place it changes.

On v0.1.7:

- CI and the contract test pin v0.1.7 and build 0.1.7-lazurio.0; the
  issue form's version example is 0.1.7-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
  v0.1.7 adds no workflow, so the swap step's list is unchanged.
- The allowlist gains toolkits/preview/handlers.ts and its test: since
  v0.1.7 preview_open takes a dev-server target (pingdotgg#28027),
  and upstream's handler answered an open with a target with the
  navigate result alone; row 10 keeps the open answer underneath, so the
  Environment browser's view stays. The fixed test gate is unchanged.
- The contract test follows the seams that moved: the settings writer
  takes the client's patch for the managed policy
  (updateAndPersistSettings, pingdotgg#27197), Hermes's runtime
  notes come from the active session setup, the MCP caller's webOrigin
  is now hostedAppUrl, the steer guard's waitsOnPendingRequest also
  holds a delegated task's question (pingdotgg#29909), and the
  ACP adapter filters T3's options through a flatMap.
- For row 30 the allowlist gains apps/web's components/ChatView.logic.ts
  and its test and components/chat/composerCommandKey.ts,
  client-runtime's state/composerDispatch.ts and its test, and
  contracts' orchestrationV2.ts: eight files with the two above. The
  contract test pins that the web keeps auto input auto while the run is
  set up; that /compact and /logout wait for no turn; that a running
  update takes the thread lock on its provider turn's first report or
  while a follow-up waits, then checks again under the lock; and that
  each follow-up gets one promotion, so a held one, one already promoted
  and a refused one stay queued without holding back the next.
- Stage 3's checkout command names the release version check's script
  and test (#165), which the v0.1.6 runbook left out.
- The runbook's Overlay table describes every row on v0.1.7, and the
  Cílový stack names each row's new commit. Main's Cílový stack still
  named older hashes from row 10 on, so the runbook and the skill now say
  to take each row's commit from main's log by subject. The runbook also
  records the Effect 4.1.2 test recipe (NodeCrypto beside NodeServices,
  ManagedPolicy.layerTest()) and that the overlay's settings writes go
  through updateSettingsWith, so the managed policy vets them.
- The runbook records what the independent check of this rebuild found:
  Codex 0.166.0, T3's managed runtime since v0.1.7, still has
  default_mode_request_user_input off by default (row 22); mcp-client
  sessions get hosted thread links on the external origin (row 20);
  upstream's star prompt now stars through the Environment's account
  (row 16); the policy lock reads the macOS and Windows sources too
  (row 18); two upstream policy paths in the update flow do not follow
  row 4's target and are offered upstream; row 30's refused promotion,
  /goal and cold-start steer; and row 33's steer page block. The overlay
  CLI tests build auth on the test managed policy.

On v0.1.8:

- CI and the contract test pin v0.1.8 and build 0.1.8-lazurio.0; the
  issue form's version example is 0.1.8-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy, whose contact is now
  security@t3.codes.
- The allowlist is unchanged. v0.1.8 adds no workflow, so the swap
  step's list is unchanged. Upstream's release-desktop.yml can now defer
  the macOS CLI's notarization with --notary-submission-file;
  lazurio-cli-archives.yml signs ad hoc, passes no such file and is
  unchanged.
- The contract test follows the seams that moved: the sidebar control
  takes showSidebar; the composer controls bar's hooks end with the
  model pick (pingdotgg#31739) and Buddy's controls return after
  them; an offered prompt suggestion comes before Buddy's placeholder
  (pingdotgg#28047); and a fresh session after /clear
  (pingdotgg#30325) never steers, in the web's dispatch mode and
  in the server's steer and promotion guards. Two new pins keep the
  Buddy surface's hides of upstream's new entries: "Use in another app"
  (decision A8) and /clear's fresh session (decision A7).
- The runbook's Overlay table describes every row on v0.1.8, the Cílový
  stack names each row's new commit and files (viewAddressCases.ts in
  rows 9 and 10), and row 30's text no longer compares
  waitsOnPendingRequest with snooze, which since v0.1.8 ignores a pending
  user_input. The runbook records this rebuild's conflicts and that a
  test the rebuild adds belongs in the row's own test file or under
  apps/*/src/lazurio/, since an upstream test file off the allowlist
  fails fork CI.

On v0.1.9:

- CI and the contract test pin v0.1.9 and build 0.1.9-lazurio.0; the
  issue form's version example is 0.1.9-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. Upstream left
  SECURITY.md unchanged, so its upstream section still equals the tag's
  policy.
- The allowlist is unchanged. The contract test's seams are unchanged
  apart from one new pin, and the tag and SHA pins move. The stack replays the approved v0.1.8 candidate
  (#187) on v0.1.9, and rows 4, 9, 15, 28 and 30 name
  their adaptations in their own messages.
- v0.1.9 adds mobile-dev-client.yml (push to main, pull_request on its
  own file and scripts/mobile-native-client.ts, workflow_dispatch); both its jobs run only in
  pingdotgg/t3code, and the swap step adds it to the workflows to
  disable after the swap. The changed ci.yml and four mobile workflows
  stay disabled.
- The runbook's Overlay table describes every row on v0.1.9, the
  Cílový stack names each row's new commit, and the runbook records
  this rebuild's conflicts and decisions. Upstream's new screen reader
  announcements (pingdotgg#33900) are capped at Buddy's messages on Buddy's
  surface, so a screen reader never hears T3's steps there (row 28);
  the contract test pins that cap in MessagesTimeline.tsx.

On v0.1.10:

- CI and the contract test pin v0.1.10 and build 0.1.10-lazurio.0; the
  issue form's version example is 0.1.10-lazurio.1. Upstream moved to
  Node 26.13.1 (pnpm 12.14.0 is unchanged), so CI, the release and the
  image pin Node 26.13.1 and node:26.13.1-bookworm by its index digest.
  Upstream left SECURITY.md unchanged, so its upstream section still
  equals the tag's policy; this row adds the fork's section to it.
- The allowlist drops branding.ts, ChatView.logic.ts and its test,
  composerCommandKey.ts and composerDispatch.ts and its test, which the
  overlay no longer changes: upstream now picks the stage label in
  branding.logic.ts, and it steers a follow-up sent before the provider
  turn started (pingdotgg#34581). Row 30 now turns an auto send
  made then into that deferred steer in Orchestrator.ts and marks it
  automatic on the queued run, so orchestrationV2.ts stays
  (#170). It adds sidebar/updateEverythingRun.tsx and its
  test, where row 4's Retry compares a Lazurio release's whole version,
  and three new upstream tests: SidebarUpdatePill.browser.test.tsx, whose rows carry
  row 4's per-row target; main.test.ts, whose stand-in window carries
  the address the prompt link capture reads (row 6); and binCli.test.ts,
  which reads row 21's `t3 thread list --json` with its total. The guard
  passes both ways on the candidate.
- The contract test follows the seams upstream moved: the launcher path
  now comes from cloud/pinnedRuntime.ts, the build stamps the page title
  from the stage label (pingdotgg#18442, and no release workflow
  sets VITE_HOSTED_APP_CHANNEL), ACP runtime instructions are one flag
  (sendRuntimeInstructions), the ACP adapter also resets unset options
  (pingdotgg#35199, held back on Buddy's instance too), provider
  hydration reads the database config (pingdotgg#34877), a
  natively resumed thread sends its unsent message
  (pingdotgg#36526), a failed send gives back the snapshot's
  draftText (pingdotgg#33124), a linked Environment's sender names
  it (pingdotgg#34721), an expandable work row's chevron sits
  between the acting-sender mark and the time (pingdotgg#35549),
  and the collapsed composer previews the prompt (pingdotgg#22148).
  Row 30's checks now pin that the one promote-to-steer is upstream's
  deferred steer, behind the pending-request guard that clears its
  steerWhenReadyRunId and steerWhenReadyIntent; the conditions under
  which an auto send in the gap becomes that steer, through
  resolveMessageDispatchIntent and the adapter's steering or
  interrupt-and-restart; and the delivery check that lets such a steer in
  only where the policy steers it then, by the session's capabilities.
- v0.1.10 adds issue-vouch.yml (issues, push to main on VOUCHED.td) and
  pr-limits.yml (pull_request_target and a daily schedule at 05:23 UTC;
  it labels, comments on and closes pull requests, dry-run without
  PR_LIMITS_ENFORCE). Both run on ubuntu-24.04 in the fork too, so the
  swap step disables them right after the swap. The swap push itself
  starts issue-vouch.yml, since it adds the workflow and VOUCHED.td, so
  the step first cancels that run and then removes any vouch label it
  gave an open issue.
- The Overlay table gains rows 35 to 37 for #214 and #216, and the
  Cílový stack names their commits on main and their files. Rows 4, 15,
  21 and 30 record the fixes from the candidate's independent check
  (#222); the rest of the table is brought up to v0.1.10
  after the release (stage 9). The runbook's "Z přestavby na v0.1.10"
  records the conflicts, the hand adaptations and those fixes, numbering
  rows as the table does, and names the replayed main (faae02a, stable
  0.1.9-lazurio.2: 0.1.9-lazurio.1 at 388b772 with #214 and #216).
- Main's #214, #216 and #220 additions to CI, the contract test and the
  runbook are carried unchanged; #216's narrow-rail pin follows row 36's
  `hidden` adaptation. A new contract pin holds row 35's hand-placed
  coordinator change: ThreadNotificationCoordinator.tsx reads hidden
  threads three times, always as listHiddenThreadKeysAtom, so Buddy's
  project's threads never sound, toast or notify.
- The review of the candidate at 50a5004 (#222) adds to
  the runbook: the contract inventory names orchestrationV2.ts with
  steerWhenReadyIntent only; rows 24 and 30 record the recorded
  followWakes and the auto steer that a question puts first in the
  queue; the F50 gate names holders.vectors.test.ts and the vendored
  Platform v0.1.22 vectors; the check that ~/.local/bin/t3 points to the
  new version reads both forms of the launcher, a symlink and since
  v0.1.10 the script posixLauncherScript writes; and the update channel
  and its procedure describe the launcher protocol's move from 3 to 4,
  which an Update from 0.1.9 passes while the 0.1.9 launcher stays until
  a local update or service install restarts the service. The contract
  test pins the copied release and the vectors' runner. After the next
  review row 24 records the wait before the send, so a repeat racing the
  first send cannot record its own; the runbook says so and drops the
  crash between send and record from the known limits. After the review
  after that, T3 records the wait only until it accepts the key's command
  and each send reads the last record after it sent, so a send that
  fails between record and dispatch leaves no wait a retry follows; the
  contract test pins the record before the send, the read after it and
  the receipt check. After the review on c5cf16b, each keyed send claims
  its key before it sends and only the claim's holder sends, so the wait
  T3 keeps is the accepted send's; the runbook describes the claim, the
  send_in_progress refusal, CLAIM_TTL_MS and the limits, and the
  contract test pins the claim, the refusal, the release, the expiry and
the receipt gate. After the review on 7b12202, only a send T3 refused
before dispatching it releases its claim (UNSENT_FAILURES), and any
other failure, such as a lost answer, keeps it until T3 accepts the
command or CLAIM_TTL_MS passes; the runbook says so in the send-state
paragraph and its limits, and the contract test pins the exact set.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.